From: Iain Sandoe <idsandoe@googlemail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Development <gcc@gcc.gnu.org>, David Malcolm <dmalcolm@redhat.com>
Subject: Re: GCC 12.1 Release Candidate available from gcc.gnu.org
Date: Sun, 1 May 2022 11:02:29 +0100 [thread overview]
Message-ID: <BC3318BA-D91C-4357-9015-1538A112807A@googlemail.com> (raw)
In-Reply-To: <Ymv3hkP1s1Zc2hj8@tucnak>
Hi Jakub,
thanks for doing the release.
> On 29 Apr 2022, at 15:34, Jakub Jelinek via Gcc <gcc@gcc.gnu.org> wrote:
>
> The first release candidate for GCC 12.1 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/
> ftp://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/
>
> and shortly its mirrors. It has been generated from git commit
> r12-8321-g621650f64fb667.
>
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux. Please test it and report any issues to bugzilla.
I have some mixed results, unfortunately.
OK:
i686, powerpc-darwin9 (bootstrapped with gcc-5.3) all supported langs.
x86_64-darwin{10..21} (bootstrapped with gcc-7.5) all supported langs.
Where I have bootstrapped D, that was using 11.3 as the bootstrap GDC.
results from:
https://gcc.gnu.org/pipermail/gcc-testresults/2022-May/760678.html
to:
https://gcc.gnu.org/pipermail/gcc-testresults/2022-May/760692.html
All of these show new fails (presumably because checking is off):
XPASS: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++98 (internal compiler error)
FAIL: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++98 (test for excess errors)
XPASS: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++14 (internal compiler error)
FAIL: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++14 (test for excess errors)
XPASS: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++17 (internal compiler error)
FAIL: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++17 (test for excess errors)
XPASS: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++20 (internal compiler error)
FAIL: c-c++-common/goacc/kernels-decompose-pr100400-1-2.c -std=c++20 (test for excess errors)
earlier x86 darwin is particularly noisy test-wise because there seem to be a lot of newer AVX512 tests
that do not check for support from the assembler etc.
====
We do not expect darwin9-11 to bootstrap with host tools, they do not have sufficient C++11 support.
However from Darwin12+ (macOS 10.8) we expect to be able to bootstrap with the host clang, but:
Not OK:
x86_64-darwin{12..15} FAIL to bootstrap with host clang, this is a regression.
the reason is that "gcc/analyzer/region-model.cc” uses initializer_lists, and it seems that <initializer_list>
is not transitively included by any used headers for _LIBCPP_VERSION < 4000. I fixed that locally by
adding initializer_list into system.h (and adding INCLUDE_INITIALIZER_LIST to the top of
gcc/analyzer/region-model.cc)
- with that change those versions do bootstrap and test OK***
OK:
x86_64-darwin{16..21} bootstrap OK with the host clang, and the test results show no surprises c.f. the
results with gcc-7.5 as the bootstrap.
If there’s an rc2 (or it seems reasonable anyway) it would be nice to fix the bootstrap with host tools.
thanks
Iain
*** I’ll do a patch for master/gcc-12 after the weekend (public holiday in the UK tomorrow), if no-one beats me to it…
next prev parent reply other threads:[~2022-05-01 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:34 Jakub Jelinek
2022-05-01 10:02 ` Iain Sandoe [this message]
2022-05-01 11:41 ` Jakub Jelinek
2022-05-01 15:38 ` Richard Biener
2022-05-01 18:06 ` Jonathan Wakely
2022-05-02 11:49 ` Boris Kolpackov
2022-05-02 12:26 ` Marc Glisse
2022-05-02 15:42 ` Jonathan Wakely
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=BC3318BA-D91C-4357-9015-1538A112807A@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@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).