Re: O2 flag in compilation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 23, 2001 at 01:36:01PM +0530, saju.pillai@oracle.com wrote:

> The -O2 flag is a compromise between maximum optimization and gcc screwing
> up. Most functions in the kernel are defined as inline functions, gcc will
> expand inline functions for you only if you give explicit optimization.
> The problem is at -O3 and above gcc will start treating some normal
> functions as inline too, so you should use -O2 at the best.

another factor is that w/o optimisation some gcc builtins such as "memset"
are not used, leading to unsatisfiable linker requirements for external memset.

Or so I believe ...

john

-- 
"There's only millions that lose their jobs and homes and sometimes accents
There's only millions that die in their bloody wars, it's alright
It's only their lives and the lives of their next of kin that they are losing
It's only their lives and the lives of their next of kin that they are losing."
	- Stereolab
-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux