public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105472] [13 regression] .note.GNU-stack breaks many Solaris/x86 tests Date: Fri, 06 May 2022 17:29:25 +0000 [thread overview] Message-ID: <bug-105472-4-7Sgpf0CmYO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105472-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105472 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I hope nobody cares about Linux a.out anymore. But #if defined(__ELF__) && defined(__linux__) .section .note.GNU-stack,"",@progbits .previous #endif is I think the most widely used way how to do it.
next prev parent reply other threads:[~2022-05-06 17:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 8:24 [Bug target/105472] New: " ro at gcc dot gnu.org 2022-05-04 8:24 ` [Bug target/105472] " ro at gcc dot gnu.org 2022-05-04 8:36 ` marxin at gcc dot gnu.org 2022-05-06 17:16 ` hjl.tools at gmail dot com 2022-05-06 17:29 ` jakub at gcc dot gnu.org [this message] 2022-05-06 18:01 ` hjl.tools at gmail dot com 2022-05-06 18:01 ` hjl.tools at gmail dot com 2022-05-09 10:15 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-05-10 16:42 ` cvs-commit at gcc dot gnu.org 2022-05-10 16:43 ` cvs-commit at gcc dot gnu.org 2022-05-10 16:51 ` cvs-commit at gcc dot gnu.org 2022-05-10 20:14 ` hjl.tools at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-105472-4-7Sgpf0CmYO@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).