Date: Wed, 13 Mar 2002 10:46:41 +0100 (CET) From: Martin Blapp <mb@imp.ch> To: Kris Kennaway <kris@obsecurity.org> Cc: Jan Stocker <jstocker@tzi.de>, <current@FreeBSD.ORG>, <hackers@FreeBSD.ORG>, <obrien@FreeBSD.ORG> Subject: Re: gcc -O broken in CURRENT Message-ID: <20020313104439.R2573-100000@levais.imp.ch> In-Reply-To: <20020312150543.A70773@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > > Here are my test news. The -O bug doesn't happen with > > gcc295 from ports ! > I tried all these FLAGS, but noone of them was creating the problems we see with -O : Optimization Options -fcaller-saves -fcse-follow-jumps -fcse-skip-blocks -fdelayed-branch -felide-constructors -fexpensive-optimizations -ffast-math -ffloat-store -fforce-addr -fforce-mem -finline-functions -fkeep-inline-functions -fmemoize-lookups -fno-default-inline -fno-defer-pop -fno-function-cse -fno-inline -fno-peephole -fomit-frame-pointer -frerun-cse-after-loop -fschedule-insns -fschedule-insns2 -fstrength-reduce -fthread-jumps -funroll-all-loops So what does -O exactly ? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020313104439.R2573-100000>