From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-announce@cygwin.com
Subject: Test: {mingw64-{i686,x86_64}-,}gcc-11.2.0-0
Date: Sat, 31 Jul 2021 19:48:40 +0200 [thread overview]
Message-ID: <87sfzuz85j.fsf@Rainer.invalid> (raw)
The native and mingw-w64 cross compilers have been updated for both
architectures to the latest upstream release version:
gcc-11.2.0-0
mingw64-i686-gcc-11.2.0-0
mingw64-x86_64-gcc-11.2.0-0.1
This is a replacement for the version 11.1 test release.
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 (including the just released binutils 2.37) and do a non-test
update in about two to four weeks.
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
reply other threads:[~2021-07-31 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87sfzuz85j.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-announce@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).