From: Ben RUBSON <ben.rubson@gmail.com>
To: "Carter, Mark Andrew (Andy)" <andy.carter@flightsafety.com>,
"cygwin-developers@cygwin.com" <cygwin-developers@cygwin.com>
Cc: Yaakov Selkowitz <yselkowi@redhat.com>
Subject: Re: Cyg32 on Win64 fails with stack-protector
Date: Mon, 25 Jun 2018 16:08:00 -0000 [thread overview]
Message-ID: <D993D876-FF05-432A-9D6B-CE0528A35FEC@gmail.com> (raw)
In-Reply-To: <fcdf2e81a317423fa53e4e976967ffd3@v0001wsxm02.flightsafety.com>
On 25 Jun 2018 17:35, Carter, Mark Andrew (Andy) wrote:
> We use Cyg32 on a Win64 system and have encountered a gcc compiler bug
> causing stack corruption due to an invalid optimized stack allocation for
> a function call that return a large structure (40 bytes). Possibly
> related to the long standing bug reported here
> "https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83116". This bug could
> bite with compiler version / switch settings or otherwise valid code
> changes.
Thank you Andy for your help.
About the bug you point to, sounds like it has been corrected in GCC 7.3 :
https://gcc.gnu.org/viewcvs/gcc/tags/gcc_7_3_0_release/gcc/cp/ChangeLog?view=markup#l30
Unfortunately I also face the issue with this GCC version.
Ben
next prev parent reply other threads:[~2018-06-25 16:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 17:12 Ben RUBSON
2018-05-29 17:01 ` Corinna Vinschen
2018-05-30 19:29 ` Bill Zissimopoulos
2018-05-31 8:19 ` Corinna Vinschen
2018-05-31 13:13 ` Ken Brown
2018-06-01 10:06 ` Corinna Vinschen
2018-06-01 10:50 ` JonY
2018-06-20 16:42 ` Ben RUBSON
2018-06-21 9:43 ` JonY
2018-06-20 16:50 ` Ben RUBSON
2018-06-20 17:21 ` Ford, Brian
2018-06-21 7:21 ` Corinna Vinschen
2018-06-23 13:50 ` Ben RUBSON
2018-06-25 9:44 ` Corinna Vinschen
2018-06-25 15:36 ` Carter, Mark Andrew (Andy)
2018-06-25 16:08 ` Ben RUBSON [this message]
2018-04-27 20:29 Bill Zissimopoulos
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=D993D876-FF05-432A-9D6B-CE0528A35FEC@gmail.com \
--to=ben.rubson@gmail.com \
--cc=andy.carter@flightsafety.com \
--cc=cygwin-developers@cygwin.com \
--cc=yselkowi@redhat.com \
/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).