From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, Helmut Zeisel <HZ2012@gmx.at>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Aw: Re: GCC 13.1 compile error when using CXXFLAGS=-std=c++20
Date: Mon, 8 May 2023 09:51:40 +0100 [thread overview]
Message-ID: <CAH6eHdRLV2e7xZyd0-C8cFixNaB4HMtQyNVVYMrRBfs1Pn+b_A@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLvU63Q1jS13jTNfyatZ8FMotUaOukh1LAey0QfZP7Yqdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]
On Mon, 8 May 2023, 09:38 NightStrike via Gcc, <gcc@gcc.gnu.org> wrote:
> On Thu, Apr 27, 2023 at 5:41 AM Jakub Jelinek via Gcc <gcc@gcc.gnu.org>
> wrote:
> >
> > On Thu, Apr 27, 2023 at 11:35:23AM +0200, Helmut Zeisel wrote:
> > > >Von: "Jakub Jelinek" <jakub@redhat.com>
> > > >An: "Helmut Zeisel" <HZ2012@gmx.at>
> > > >Cc: gcc@gcc.gnu.org
> > > >Betreff: Re: GCC 13.1 compile error when using CXXFLAGS=-std=c++20
> > > >On Thu, Apr 27, 2023 at 11:09:19AM +0200, Helmut Zeisel via Gcc wrote:
> > > >> I compiled GCC 13.1.0 with GCC 12 and had the environment variable
> CXXFLAGS set to -std=c++20
> > > >> This gives the error (both linux and cygin)
> > > >>
> > > >> gcc-13.1.0/libstdc++-v3/src/c++98/bitmap_allocator.cc:51:23: error:
> ISO C++17 does not allow dynamic exception specifications
> > > >> 51 | _M_get(size_t __sz) throw(std::bad_alloc)
> > > >>
> > > >> After
> > > >>
> > > >> unset CXXFLAGS
> > > >>
> > > >> compilation works
> > >
> > > >Don't do it.
> > >
> > > Dont do *what*?
> > > export CXXFLAGS=... ?
> >
> > Include explicit -std= settings in such exported variables, especially
> when
> > building GCC. Packages should decide themselves in which language
> version
> > they are written in, or if they are written in common subset, they should
> > just defer to the compiler default.
> > Note, doing that would break building even much older GCC versions.
>
> Maybe configure should catch that?
>
> diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac
> index 0dd550a4b4b..f0d998aad94 100644
> --- a/libstdc++-v3/configure.ac
> +++ b/libstdc++-v3/configure.ac
> @@ -86,6 +86,9 @@ AH_TEMPLATE(VERSION, [Version number of package])
> # -fno-builtin must be present here so that a non-conflicting form of
> # std::exit can be guessed by AC_PROG_CXX, and used in later tests.
>
> +AS_CASE(["$CXXFLAGS"],
> + [*-std=*], [AC_MSG_ERROR([don't do that])])
> +
> save_CXXFLAGS="$CXXFLAGS"
> CXXFLAGS="$CXXFLAGS -fno-builtin"
> AC_PROG_CC
>
Seems like a reasonable idea at first glance, somebody could test and
submit a patch.
That pattern will match a hypothetical option like -ffoo-std=bar which is
not a -std option. I think a better pattern would be needed.
prev parent reply other threads:[~2023-05-08 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 9:09 Helmut Zeisel
2023-04-27 9:22 ` Jakub Jelinek
2023-04-27 9:35 ` Aw: " Helmut Zeisel
2023-04-27 9:40 ` Jakub Jelinek
2023-05-08 8:38 ` NightStrike
2023-05-08 8:51 ` Jonathan Wakely [this message]
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=CAH6eHdRLV2e7xZyd0-C8cFixNaB4HMtQyNVVYMrRBfs1Pn+b_A@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=HZ2012@gmx.at \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=nightstrike@gmail.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).