diff options
| author | Linus Torvalds <[email protected]> | 2007-05-17 20:18:11 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2007-05-17 20:18:11 -0700 |
| commit | b46522394dde7341a5253658096f354b65cbd90d (patch) | |
| tree | c8631b9d3c07b4fd60f27e1c89863e89247d0eb7 /tools/perf/scripts/python | |
| parent | b42895d6fe66995ab101c15d9a59c78474dbf382 (diff) | |
Revert "[PATCH] x86: Drop cc-options call for all options supported in gcc 3.2+"
This reverts commit c8fdd247255a3a027cd9f66dcf93e6847d1d2f85.
It turns out the kernel was correct, and the gcc complaint was a gcc
bug. The preferred stack boundary is expressed not in bytes, but in the
the log2() of the preferred boundary, so "-mpreferred-stack-boundary=2"
is in fact exactly what we want, but a gcc that is compiled for x86-64
will consider it an error (because the 64-bit calling sequence says that
the stack should be 16-byte aligned) even if we are then using "-m32" to
generate 32-bit code.
Noted-by: Mikulas Patocka <[email protected]>
Cc: Jan Hubicka <[email protected]>
Acked-by: Andi Kleen <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions