On Mon, Nov 25, 2002 at 09:03:58AM -0500, David Walter wrote: > On IRC someone (when I first found this problem) had dismissed this as > a 'feature' of my build, I accepted this, but continue to build w/o > optimization. > > But in looking gcc3.* already had bugs posted against it for > optimization problems under some circumstances. > > AFAIK this hasn't changed with gcc.
Well, certainly there can be bugs in gcc's optimization. We won't know before looking at the reason of the hang and possibly looking at the generated code. > I would have posted a bug against gcc or the Hurd or both if > appropriate and considered posting one, but for the dismissal. The first step is to file it against the Hurd, including all the information you have. As soon as someone comes to looking at it, it can be reassigned or forwarded if it turns out not to be a bug in our programs. > Is the appropriate course to post a bug against, the Hurd for using > - -O3, gcc for the problem and the mount command itself? Where should > these be posted, bug-hurd? bug-hurd, and/or the Savannah bug tracking system for the Hurd (see savannah.gnu.org/projects/hurd). The bug tracking system has the advantage that it won't get lost, the mailing list has the advantage that people actually read it :) > Does gcc need another bug report for this particular program failure? You can not say this without looking at the actual reason for the hang. Thanks, Marcus -- `Rhubarb is no Egyptian god.' GNU http://www.gnu.org [EMAIL PROTECTED] Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/ [EMAIL PROTECTED] http://www.marcus-brinkmann.de/ _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
