public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dwmw2 at infradead dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/67169] New: -fstack-check=no doesn't disable stack checking Date: Mon, 10 Aug 2015 11:12:00 -0000 [thread overview] Message-ID: <bug-67169-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67169 Bug ID: 67169 Summary: -fstack-check=no doesn't disable stack checking Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dwmw2 at infradead dot org Target Milestone: --- $ echo 'void foo(void) { char lots[8192]; }' | i686-w64-mingw32-gcc -S -o- -xc - -fstack-check=no .file "" .text .globl _foo .def _foo; .scl 2; .type 32; .endef _foo: pushl %ebp movl %esp, %ebp movl $8192, %eax call ___chkstk_ms subl %eax, %esp nop leave ret .ident "GCC: (GNU) 5.1.0 20150422 (Fedora MinGW 5.1.0-2.fc22)" This is causing me problems when building the EDK II UEFI implementation. Building that with MinGW is useful because it reproduces a number of LLP64-related issues which would otherwise require Windows to discover. If I use '-fstack-check=specific' *that* does seem to do what I want. But I'm not sure I should be suggesting that as an upstream fix for the MinGW build, because it seems wrong.
next reply other threads:[~2015-08-10 11:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-10 11:12 dwmw2 at infradead dot org [this message] 2015-08-15 11:48 ` [Bug target/67169] " pinskia at gcc dot gnu.org 2015-08-15 13:27 ` dwmw2 at infradead dot org 2015-09-10 7:35 ` ebotcazou at gcc dot gnu.org 2015-09-10 8:45 ` dwmw2 at infradead dot org 2015-09-10 8:58 ` [Bug target/67169] add an option to disable stack checking on x86 for UEFI ebotcazou at gcc dot gnu.org
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-67169-4@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).