From: Jonathan Yong <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Test: {mingw64-{i686,x86_64}-,}gcc-11.1.0-0.1
Date: Wed, 12 May 2021 10:42:08 +0000 [thread overview]
Message-ID: <0c2f908b-d3ac-5bd6-92b1-c2bd0970ec24@gmail.com> (raw)
In-Reply-To: <f3f9f296-cde2-1549-e7e9-38c1c855d5df@towo.net>
On 5/12/21 9:14 AM, Thomas Wolff wrote:
> Am 10.05.2021 um 21:13 schrieb Achim Gratz:
>> The native and mingw-w64 cross compilers have been updated for both
>> architectures to the latest upstream release version:
>>
>> gcc-11.1.0-0.1
> Are there any known problems with gcc 11? My program crashes if compiled
> with gcc -O2; gcc -O1 works, gcc 10 also works.
> Thomas
>
>> mingw64-i686-gcc-11.1.0-0.1
>> mingw64-x86_64-gcc-11.1.0-0.1
>>
>> This test release includes libgccjit as a separate package for the
>> native toolchain on both architectures. Since Cygwin can't use ASLR any
>> nontrivial dynamic objects that get created in this way will likely need
>> to get rebased before they can be used (especially on 32bit). It is
>> unlikely that build systems recognize the need for doing that at the
>> moment.
>>
>> Please test these compilers with your packages and applications as
>> extensively as possible (especially if you are a Cygwin package
>> maintainer). Unless problems are found that necessitate another round
>> of testing, the plan is to bootstrap the support libraries with the new
>> toolchain and do a non-test update in about two to four weeks.
>>
>
>
Does stripping the optimized executable fix things? Are you also able to
produce a minimal test case?
next prev parent reply other threads:[~2021-05-12 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 19:13 Achim Gratz
2021-05-12 9:14 ` Thomas Wolff
2021-05-12 10:42 ` Jonathan Yong [this message]
2021-05-12 18:30 ` Thomas Wolff
2021-05-13 1:41 ` Brian Inglis
2021-05-13 2:22 ` Thomas Wolff
2021-05-12 18:53 ` Achim Gratz
2021-05-13 8:57 ` Thomas Wolff
2021-05-13 19:33 ` Hans-Bernhard Bröker
2021-05-13 21:57 ` Thomas Wolff
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=0c2f908b-d3ac-5bd6-92b1-c2bd0970ec24@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.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).