John Myers posted <[EMAIL PROTECTED]>, excerpted below, on Wed, 08 Feb 2006 18:49:54 -0800:
> On Wednesday 08 February 2006 16:41, Kevin F. Quinn (Gentoo) wrote: >> On x86 this is not enabled since it interferes with debugging (info gcc >> isn't too clear on this, it's mentioned on the description of '-O') - >> is this different from amd64 (I'm still x86-only :/ )? > x86_64 does not require frame pointers for debugging, so > -fomit-frame-pointer is enabled with -O /Click/. THAT'S the reason I hadn't removed the potentially redundant -fomit-frame-pointer! I'd forgotten about that, but the manpage /does/ mention that it's only enabled with -O<whatever> where it won't interfere with debugging, and I was unsure of whether that was the case on x86_64/amd64 or not, so I left it in. Knowing that it doesn't interfere with debugging on amd64, and is therefore enabled by -O<whatever>, I could probably remove the redundancy, now. ... Or rather, I could, if I was running a no-multilib subprofile. I don't do a lot of x86 compiling (and have a policy of not running binary-only stuff either, so that means I don't have much x86 32-bit on my system), but as I'm on the standard multilib-by-default profile (actually, I'm already on the still unreleased 2006.0, having diffed it and 2005.1 and decided I might as well do so when I finally upgraded from 2005.0, skipping 2005.1 entirely), gcc/glibc/sandbox and the like have 32-bit compiled elements, as does grub, of course, so maybe I better leave it in, after all. Actually, grub is really the only thing really keeping me from going no-multilib profile, but as I said, I don't like running binary-only stuff, and that extends to grub-static as well since there's an alternative, which means I'm supporting a LOT of 32-bit overhead in terms of maintaining that multilib toolchain, all so I can compile ONE single program, grub, from source. OTOH, being a bootloader, grub /is/ rather critical to my machine's operation, even if only for a few seconds every few weeks or whenever it is that I decide to reboot. However, now, having had this discussion, I'll be clearer on all the implications of -fomit-frame-pointer, and remember exactly why I chose to keep it in my CFLAGS -- it boils down to 32-bit compatibility. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-amd64@gentoo.org mailing list
