[Octave-bug-tracker] [bug #62212] Issues when casting large integers to floating point

[Markus Mützel]

Follow-up Comment #17, bug #62212 (project octave):

Forgot to mention: There might still be places in the code base where floating
point values are compared to int_min. That should be ok on platforms that use
two's complement for negative integers (the vast majority afaict). They might
need to be adapted if Octave runs on a platform that uses ones' complement for
negative integers. (Are those even still around?)
Since all of our CI runs on systems with two's complement, the compiler is
silent about those potential errors. (At least, I presume that is the
reason.)
I only changed it where I "accidentally" stumbled across it.

We have checks for ones' complement in some locations. If someone cares, they
are welcome to try and track down where we would need changes for those
platforms. Those are likely locations where we cast int_min to a floating
point.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62212>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/