From owner-freebsd-hackers Mon Apr 17 8:35:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ewok.creative.net.au (fuzzy.aussie.com.au [203.30.44.82]) by hub.freebsd.org (Postfix) with SMTP id 4563337B5CB for ; Mon, 17 Apr 2000 08:35:54 -0700 (PDT) (envelope-from freebsd@ewok.creative.net.au) Received: (qmail 66306 invoked by uid 1008); 17 Apr 2000 15:35:48 -0000 Date: Mon, 17 Apr 2000 23:35:48 +0800 From: Adrian Chadd To: Martin Cracauer Cc: hackers@freebsd.org Subject: Re: What are the best gcc optimization options for Pentium 200 MMX Message-ID: <20000417233547.E59015@ewok.creative.net.au> References: <86snwuwk9w.fsf@not.demophon.com> <20000410190151.A18146@ewok.creative.net.au> <20000417140725.A6672@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000417140725.A6672@cons.org>; from Martin Cracauer on Mon, Apr 17, 2000 at 02:07:25PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 17, 2000, Martin Cracauer wrote: j > > I have exactly the same problem hacking squid code under 4.0-CURRENT > > and 5.0-CURRENT. Basically, inside the dns routines a variable > > would be corrupted between a couple of non-relevant lines, and cause > > squid to segfault after trying to resolve anything. Taknig out -O2 > > and replacing it with -O causes the same problem. Its annoying. :( > > Could you pleaseverify whether that looks like PR bin/16862? > > If they are releated, you need to change the optimization setting of > the shared libraries (or generally -fpic code) your crashing code > uses, not the setting of the code itself. Raising the optimization > setting may as well help as lowering it. > > Basically, our gcc produces code our as doesn't understand and symbol > locations in -fpic code may be damaged, so that access (read or write) > to such a variable causes segmentation violations. > > Are there any as warning messages (especially GOTOFF - related ones) > when you compile the code in question, especially when compiling > shared libraries it may use? > > It sounds like you found the lines where the corruption happens, I > would welcome the exact locations. I'd like to hunt this one down. > Its squid's DNS routines, not the shared libraries. heck the squid-dev archies on http://www.squid-cache.org/, as someone found the lines of asm which are wrongly generated. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message