From owner-freebsd-current Thu Jun 13 17:58:51 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 83DBA37B40D; Thu, 13 Jun 2002 17:58:46 -0700 (PDT) Date: Thu, 13 Jun 2002 17:58:46 -0700 From: Juli Mallett To: Terry Lambert Cc: Alex Zepeda , Bruce Evans , current@freebsd.org Subject: Re: Broken world in rtld-elf... Message-ID: <20020613175846.A70861@FreeBSD.ORG> References: <20020612231541.GA1543@blarf.homeip.net> <20020613121920.T1422-100000@gamplex.bde.org> <20020613191637.GA57841@blarf.homeip.net> <3D093302.42B0E0F6@mindspring.com> <20020613172608.C62694@FreeBSD.ORG> <3D093CB7.94D5EBC3@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <3D093CB7.94D5EBC3@mindspring.com>; from tlambert2@mindspring.com on Thu, Jun 13, 2002 at 05:45:43PM -0700 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , X-Affiliated-Projects: FreeBSD, xMach, ircd-hybrid-7 X-Towel: Yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Terry Lambert escriurères > Juli Mallett wrote: > > Errr, it was with 0 level optimisation that is the problem, not a real > > level. Read carefully what bde said, and look at hte warnings and how > > GCC deals with the code in question. > > > > Also, your example is very wrong, read make(1)'s section on dealing with > > variables. > > > I know my example is very wrong; though it could be used to grep > for optimizer flags, where it could not be used for what I jokingly > said it could be used for... I guess it was too subtle. > > Question: > > -O0 fails to produce good code; how do I check and warn if > -O0 is being used? > > Answer: > > Fix -O0, or grep its use and complain about it .if "${MACHINE_ARCH}" == "i386" CFLAGS:= $(CFLAGS:N-O0) .endif I think. > Answer 2: > > Make its use an argument error to the compiler, until it is > fixed -O0 isn't broken, it just doesn't handle this construct right, and the issue is known. > Answer 3: > > Quit munging the Makefiles, when they will just need to be > unmunged later, and the problem goes away if you change > the compiler NetBSD and OpenBSD do this to work around crappy toolchains all the time. Most of the time it's to *enable* -O0 though, ironically :) -- Juli Mallett FreeBSD: The Power To Serve Perception is prejudice / Don't classify me / Accept me as me / Not what you see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message