GCC 103863, We need a warning for loss of no-exec stacks
Jeffrey Walton
noloader@gmail.com
Thu Dec 30 02:40:55 GMT 2021
On Wed, Dec 29, 2021 at 9:27 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Wed, Dec 29, 2021 at 6:25 PM Jeffrey Walton via Binutils
> <binutils@sourceware.org> wrote:
> >
> > Would anyone like to comment on this GCC feature request:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103863 .
> >
> > The reason I'm bringing it here is, AP suggested a warning should be
> > in the linker (which combines object files), and not the compiler
> > (which creates object files).
>
> GCC does not create the object files from assembly code either (since
> it is the case you are worried about really) :). It is the assembler
> (gas) which is still part of binutils.
Thanks Andrew.
In the case of ASM files, that's true. But GCC is often the driver.
People interact with GCC, not GAS. Since GCC is the compiler driver
and supervises the build, GCC seems like a natural place to enable a
warning for users.
I think the linker would be a good place, too. I think the more
chances you give someone to catch a mistake, the better.
Jeff
More information about the Binutils
mailing list