--- Comment #1 from cube at cubidou dot net 2009-11-08 20:27 ---
Created an attachment (id=18995)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18995action=view)
Test case
This very simple C file will expose the bug. In the assembler output, see how
only 152 is substracted to
--- Comment #2 from pinskia at gmail dot com 2009-11-08 20:29 ---
Subject: Re: New: Incorrect stack setup on x86_64
The x86_64 abi includes a red zone. So I doubt this a bug in gcc
unless netbsd's abi does not match what gcc does.
Sent from my iPhone
On Nov 8, 2009, at 12:25 PM,
--- Comment #3 from cube at cubidou dot net 2009-11-08 20:37 ---
Subject: Re: Incorrect stack setup on x86_64
On Sun, Nov 08, 2009 at 08:29:44PM -, pinskia at gmail dot com wrote:
--- Comment #2 from pinskia at gmail dot com 2009-11-08 20:29 ---
Subject: Re: New:
--- Comment #4 from cube at cubidou dot net 2009-11-08 20:38 ---
Subject: Re: Incorrect stack setup on x86_64
On Sun, Nov 08, 2009 at 08:37:25PM -, cube at cubidou dot net wrote:
[...]
152 is too small even for the total size of the local variables (268 in
I meant 260 here.
--
--- Comment #5 from cube at cubidou dot net 2009-11-08 20:56 ---
Ok, I get it now. Not a gcc bug, we have to compile our kernel modules with
-fno-red-zone like the rest of the kernel.
Sorry for the noise.
--
cube at cubidou dot net changed:
What|Removed
