http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47571
--- Comment #31 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> 2011-03-11 16:45:31 UTC ---
> That being said, I'd prefer to postpone this fix to stage 1 due to
>
> - I'm currently moving flats so my stuff is all over and I'm very busy
> - AFAIU 4.6 release is imminent?
> - I lack the ability to test all weird and wonderful targets.
> - This close to release I'd very much like to avoid regressions in primary or
> secondary targets.
> - As can be seen in the reopening of this PR, for less used targets there
> might
> anyway be a month latency between something landing in trunk and getting test
> reports.
Not really: the delay was caused because the test system broke and it
took me quite some time to get myself a replacement. Normally, I
bootstrap everywhere once a week and analyse results.
> Thus, I'd suggest fixing this in stage 1, then, after getting reports that the
> fix works, backport hopefully in time for 4.6.1.
>
> Of course, the above is only my own justifications and constraints; if someone
> else wants to fix it ASAP, go right ahead.
I'd really like to see this fixed before 4.6.0: it is a regression from
4.5 and makes fortran completely unusable on Tru64 UNIX for a relatively
minor gain on other platforms. If all else fails, I'd go as far as
advocating to revert the patch that introduced clock_gettime (and quite
late in the release cycle, I might say).
Sorry for being so late to reply: I've been totally swamped this week.
Thanks.
Rainer
