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 target/67169] -fstack-check=no doesn't disable stack checking
Date: Sat, 15 Aug 2015 13:27:00 -0000 [thread overview]
Message-ID: <bug-67169-4-C9QJa51Dvb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67169-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67169
--- Comment #2 from David Woodhouse <dwmw2 at infradead dot org> ---
(In reply to Andrew Pinski from comment #1)
> I suspect i686-w64-mingw32 can never be used for self host binaries.
It has been. EDKII has toolchain configurations for it:
http://tianocore.sourceforge.net/wiki/Unix-like_systems#Build_gcc_x64_UEFI_cross_compiler
next prev parent reply other threads:[~2015-08-15 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 11:12 [Bug c/67169] New: " dwmw2 at infradead dot org
2015-08-15 11:48 ` [Bug target/67169] " pinskia at gcc dot gnu.org
2015-08-15 13:27 ` dwmw2 at infradead dot org [this message]
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-C9QJa51Dvb@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: link
Be 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).