public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98729] [11 Regression] GCC 11 MinGW Windows build doesn't generate working PE executables
Date: Mon, 01 Feb 2021 17:39:53 +0000 [thread overview]
Message-ID: <bug-98729-4-c4WjtG3LFO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98729-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98729
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2021-02-01
--- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I don't know what this section does, but I did notice it contains a
> reference to `cygwin.S`, which I didn't expect to see in a pure MinGW binary.
The file just implements the stack checking routine mandated by Windows.
Can you post the list of sections given by objdump?
next prev parent reply other threads:[~2021-02-01 17:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:29 [Bug c/98729] New: " brechtsanders at users dot sourceforge.net
2021-01-18 14:32 ` [Bug c/98729] " brechtsanders at users dot sourceforge.net
2021-01-18 16:40 ` [Bug target/98729] " pinskia at gcc dot gnu.org
2021-01-18 17:16 ` brechtsanders at users dot sourceforge.net
2021-01-19 7:38 ` [Bug target/98729] [11 Regression] " rguenth at gcc dot gnu.org
2021-01-19 7:41 ` rguenth at gcc dot gnu.org
2021-01-19 19:06 ` brechtsanders at users dot sourceforge.net
2021-01-19 19:06 ` brechtsanders at users dot sourceforge.net
2021-01-20 9:23 ` brechtsanders at users dot sourceforge.net
2021-01-20 12:40 ` brechtsanders at users dot sourceforge.net
2021-02-01 17:39 ` ebotcazou at gcc dot gnu.org [this message]
2021-02-02 8:51 ` brechtsanders at users dot sourceforge.net
2021-02-02 12:05 ` ebotcazou at gcc dot gnu.org
2021-02-09 20:21 ` redi 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-98729-4-c4WjtG3LFO@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).