> I wouldn't care if CONFIG_CC_OPTIMIZE_FOR_SIZE was hidden behind > CONFIG_EMBEDDED, but as long as it's available as a general purpose > option we have to consider it's performance.
I think you are missing the point. You tell the kernel to OPTIMIZE_FOR_SIZE. *over performance*. Sure. Performance shouldn't be EXTREMELY pathetic, but it's not; and if it were, it's a problem with the gcc version you have (and if you are a distro, you can surely fix that) > > The interesting questions are: > Does -Os still sometimes generate faster code with gcc 4.2? > If yes, why? on a system level, size can help performance because you have more memory available for other things. It also reduces download size and gives you more space on the live CD.... if you want to make things bigger again, please do this OUTSIDE the "optimize for size" option. Because that TELLS you to go for size. -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
