public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/106482] [12/13 Regression] bootstrap of 12.1.0 using 4.8.2 fails with C++ errors
Date: Thu, 22 Dec 2022 14:53:11 +0000 [thread overview]
Message-ID: <bug-106482-4-ilo0Bqpe4C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106482-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106482
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Priority|P3 |P2
Ever confirmed|0 |1
Last reconfirmed| |2022-12-22
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Daniel Richard G. from comment #2)
> It would be good to have a specific minimum version of GCC in the documented
> prerequisites, as the current text ("an existing GCC binary (version 4.8 or
> later)", albeit referring to non-bootstrap builds) misses edge cases like
> this.
Note the documented requirement for bootstrapping is a "ISO C++11 compiler".
We fail to specifically say which GCC version fulfills this, the GCC 4.8
requirement for non-bootstrap is technically unrelated but it will run into
the same issues I think.
Generally when we refer to a major GCC version picking the latest bugfix
release is always recommended.
I'm posting a proposal to amend the documentation.
next prev parent reply other threads:[~2022-12-22 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 9:57 [Bug bootstrap/106482] New: [12 " skunk at iskunk dot org
2022-08-01 9:14 ` [Bug bootstrap/106482] " rguenth at gcc dot gnu.org
2022-08-01 9:31 ` skunk at iskunk dot org
2022-12-22 14:53 ` rguenth at gcc dot gnu.org [this message]
2022-12-22 15:01 ` [Bug bootstrap/106482] [12/13 " cvs-commit at gcc dot gnu.org
2022-12-22 15:02 ` cvs-commit at gcc dot gnu.org
2022-12-22 15:02 ` rguenth at gcc dot gnu.org
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=bug-106482-4-ilo0Bqpe4C@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).