#8773: GCC-4.5.0 breaks GAP -- the workspace is broken, hence gap('2+2') fails.
----------------------+-----------------------------------------------------
   Reporter:  was     |       Owner:  GeorgSWeber                              
       Type:  defect  |      Status:  needs_work                               
   Priority:  major   |   Milestone:  sage-4.4.1                               
  Component:  build   |    Keywords:                                           
     Author:          |    Upstream:  Reported upstream. Little or no feedback.
   Reviewer:          |      Merged:                                           
Work_issues:          |  
----------------------+-----------------------------------------------------

Comment(by wjp):

 Replying to [comment:6 dimpase]:
 > this needs to be tested on every platform Sage supports, (itaniums,
 macs, sparcs...).
 >
 > This is quite a drastic change, and there is no telling how older
 versions of gcc would cope!

 Not so drastic, really. The changes are very much localised, and the new
 code is *far* less risky than the current version. Older versions of gcc
 should have no problem with it.I agree it needs testing on more platforms,
 of course.

 > I think it should get seen by real GAP kernel folks before we start even
 think of shipping this.
 >
 > Should I post this on GAP-support, of which I happen to be a member?

 If you could, that would be great. Thanks.


 > I would also propose another way to get it in Sage:   make these new
 patches conditional on gcc version >=4.5.

 In my opinion writing such a check would cause more potential for trouble
 than the changes.

 -Willem Jan

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8773#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to