From owner-freebsd-current Wed Mar 15 17:39:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id CEAE737BB33 for ; Wed, 15 Mar 2000 17:39:16 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id CAA08528 for freebsd-current@freebsd.org; Thu, 16 Mar 2000 02:39:14 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA18433 for freebsd-current@freebsd.org; Thu, 16 Mar 2000 01:10:55 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: gcc -Os optimisation broken (RELENG_4) Date: 16 Mar 2000 01:10:54 +0100 Message-ID: <8ap8qe$hvj$1@bigeye.rhein-neckar.de> References: <38CF48CF.59A100D7@altavista.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > I've just upgraded my production server to the 4.0-RELEASE and found that > squid23 when compiled with -Os option dying with signal 11 on each attempt to > load page. When I recompiled it with -O fault disappeared. Which brings us back to the popular topic of which optimization levels are reliable. Building 5.0-CURRENT with "-Os -mpentium" failed for me with gas complaining (unknown opcode I think, but don't hold me to it). I went back to "-O -mpentium" and that worked fine. On another machine, "-O2 -mpentiumpro" worked, too. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message