On Apr 21, 2:20 am, Francois <[EMAIL PROTECTED]> wrote: <SNIP>
> Apparently this is an optimization bug again with gcc4.3, we have > some > reports on it in gentoo > bugzilla:http://bugs.gentoo.org/show_bug.cgi?id=54738#c27 > It shows up at a different place than gcc4.2.2 but forcing -O0 the > same > way solve the problem. Funny how gcc4.2.3 was fixed but 4.3 fails > again. Yeah, the plane is to force "-O0" and hopefully kill this problem once and for all. Ironically it has bitten us on Itanium and now some Athlon, while it worked perfectly fine with gcc 4.3 on some Xeons we tested. Go figure ;) It is unclear if this fix will make it into 3.0, but it will in any case make it into 3.0.1 if it doesn't make it into 3.0. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
