Tim, All
Looks like the Trinity code is invalid:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723#c6
On 02/14/2011 01:44 PM, David C. Rankin wrote:
Tim, All
Looks like the Trinity code is invalid:
The discussion regarding the bug pretty interesting. The jury is still out on whether this is a gcc issue or a trinity issue. There is no question that gcc was changed and that this change means that trinity will not compile on the new gcc. The open question is whether it is Trinty or gcc that needs to change to fix the issue.
Tim, All
Looks like the Trinity code is invalid:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723#c6
-- David C. Rankin, J.D.,P.E.
Saw that. I'll be fixing SVN shortly.
Tim
On 02/14/2011 04:53 PM, Timothy Pearson wrote:
Tim, All
Looks like the Trinity code is invalid:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723#c6
-- David C. Rankin, J.D.,P.E.
Saw that. I'll be fixing SVN shortly.
Tim
Thanks Tim,
You guys are great. I'll wait for the updates and then dive back in with gcc 4.5.2. The gcc bug was a neat issue. You can see how a simply change to bring the g++ compiler into compliance with standards can reap havoc on existing code. Surprisingly, I understood the issue (the details of which were way over my head). But, the change to gcc in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11764 resulting in gcc >= 4.5 not accepting the existing class constructor made sense.
What? - Trinity building on the new gcc? Looks like we have us a modern day desktop in the works :p
-
David C. Rankin -
Timothy Pearson