Ticket #663 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

get flint into SAGE!!

Reported by: was Owned by: was
Priority: major Milestone: sage-2.8.5
Component: packages Keywords:
Cc: Author(s):
Report Upstream: Reviewer(s):
Merged in: Work issues:

Description


Change History

Changed 3 years ago by was

Problems with gcc-3.3:

3:58 < williamstein> mabshoff -- regarding gcc and flint -- shouldn't sage still work with gcc-3.3?
13:59 < williamstein> I.e., so far SAGe doesn't require gcc-3.4, so shouldn't we make it so flint can work with gcc-3.3.
13:59 < williamstein> Or?
13:59 < mabshoff> Well, gcc 3.3.x is a decent compiler.
13:59 < mabshoff> So it should work, and there are some workarounds for the problems in FLINT.
14:02 < mabshoff> well:
14:02 < mabshoff>  GCC provides built-in versions of the ISO C99 floating point comparison
14:02 < mabshoff> macros that avoid raising exceptions for unordered operands.  They have
14:02 < mabshoff> the same names as the standard macros ( `isgreater', `isgreaterequal',
14:02 < mabshoff> `isless', `islessequal', `islessgreater', and `isunordered') , with
14:02 < mabshoff> `__builtin_' prefixed.  We intend for a library implementor to be able
14:02 < mabshoff> to simply `#define' each standard macro to its built-in equivalent.

Changed 3 years ago by was

  • status changed from new to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.