[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: %gs:0x14
From: |
Samuel Thibault |
Subject: |
Re: %gs:0x14 |
Date: |
Tue, 14 Nov 2006 16:26:26 +0100 |
User-agent: |
Mutt/1.5.11 |
Thomas Schwinge, le Tue 14 Nov 2006 16:15:08 +0100, a écrit :
> Using `-fstack-protector' with GCC 4.1 made it include assembler code
> using ``%gs:0x14'' even with `-ffreestanding'. However, this isn't the
> correct thing to do in kernel
> space (with `-ffreestanding'). I think I've now tracked where this is
> coming from. This is not an issue anymore with GCC 4.2 or a GCC 4.1 that
> is recent enough,
You mean that gcc now correctly switches to using __stack_chk_guard in
freestanding mode?
> But then, if this was `*-*-*gnu*' instead of `*-*-linux*' in the above
> configure check, I guess that the smashing stack protector wouldn't work
> (and would instead make all compiled programs crash) in user space on
> GNU/Hurd then, as then not `[GCC]/gcc/libgcc/''s generic code would be
> used, but instead the Linux-tls-specific macros.
Well, we'll have to fix GNU/Hurd's TLS someday anyway.
Samuel
- Re: %gs:0x14, Thomas Schwinge, 2006/11/14
- Re: %gs:0x14,
Samuel Thibault <=
- Re: %gs:0x14, Thomas Schwinge, 2006/11/14
- Re: %gs:0x14, Thomas Schwinge, 2006/11/14
- Re: %gs:0x14, Neill Miller, 2006/11/14
- Re: %gs:0x14, Samuel Thibault, 2006/11/14
- Re: %gs:0x14, Neill Miller, 2006/11/14
- Re: %gs:0x14, Samuel Thibault, 2006/11/14
- Re: %gs:0x14, Neill Miller, 2006/11/14
Re: %gs:0x14, Thomas Schwinge, 2006/11/15
Re: %gs:0x14, Roland McGrath, 2006/11/22