On Mon, Sep 23, 2002 at 11:08:13AM -0400, Alexander Kabaev <[EMAIL PROTECTED]> wrote:
> > Heh, this sounds like a joke.. because I have written at least three > > messages to -current list about the very same thing. I know that > > following -current list for day-to-day basis is challenge, but > > nevertheless this surprises me. Seems like nobody has read my > > messages nor find the cause of this failure interesting. Yes this > > caused bu machine type optimisation and everybody who's brave enough > > to set CPUTYPE=p[234] will be trapped. > > You might want to report the bug to GCC developers first instead of > sending your complaints here. Some help finding the offending function > and providing people with additional information will come a long way > toward having this bug finally fixed. Please consult > http://gcc.gnu.org/bugs.html for instructions if you decide to do so. I'm not complaining, only reporting what I found. It's quite unfair for non-developer to complain about development track, IMHO. I'll see what I can do, but finding offending function is probably beyond my knowledge. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
