This is the mail archive of the cygwin-developers mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Cyg32 on Win64 fails with stack-protector

From: Ben RUBSON <ben dot rubson at gmail dot com>
To: "Carter, Mark Andrew (Andy)" <andy dot carter at flightsafety dot com>, "cygwin-developers at cygwin dot com" <cygwin-developers at cygwin dot com>
Cc: Yaakov Selkowitz <yselkowi at redhat dot com>
Date: Mon, 25 Jun 2018 18:08:46 +0200
Subject: Re: Cyg32 on Win64 fails with stack-protector
References: <8A9D918F-F233-48DA-9B98-B87D7B188C21@gmail.com> <20180529165958.GK3501@calimero.vinschen.de> <DDEADFF6-DFDE-4885-8134-7E6937B86C2A@gmail.com> <20180625094448.GF28757@calimero.vinschen.de> <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 bugcausing stack corruption due to an invalid optimized stack allocation fora function call that return a large structure (40 bytes). Possiblyrelated to the long standing bug reported here"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83116";. This bug couldbite with compiler version / switch settings or otherwise valid codechanges.


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

References:
- Re: Cyg32 on Win64 fails with stack-protector
  - From: Ben RUBSON
- Re: Cyg32 on Win64 fails with stack-protector
  - From: Corinna Vinschen
- RE: Cyg32 on Win64 fails with stack-protector
  - From: Carter, Mark Andrew (Andy)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]