Summary: | gcc-3.2.3-r1 - kernel compile with -Os breaks XFS recovery | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cory Visi (RETIRED) <merlin> |
Component: | [OLD] GCC Porting | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | azarah, george, rickardm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Cory Visi (RETIRED)
2003-09-23 08:16:57 UTC
Generally, one should not touch kernel compiliations commands. -O2 has been certified to work perfectly with the kernel. -Os uses -O2, but eliminates certaion options that increase code size, so it is possble this is disabling a segment of code in XFS Recovery that relies on an option specified by -O2 but not -Os. -Os also enables specific optimizations that reduce code size. Unless you're compiling for an embedded environment, I'd advise leaving the -O2 parameter intact to the kernel, and instead reccommend stripping the kernel of any .comment and .note sections via the strip command as follows: strip -R .comment -R .note <uncompressed kernel image> Resolving as INVALID as there really isn't anything that can be done with this bug. It is likely a generic gcc bug or kernel issue that may or may not be related to Gentoo, but there is not enough information to determine the case. As per Comment #1, it is recommended to try stripping the kernel if you are concerned about code-size. The one kernel I have tried building with -Os didn't even boot. I'd just like to point out that Gentoo used the -Os flag in its kernels as late as 2.4.19. It was part of the "gentoo" diff included in the patchset. |