From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Jakub Jelinek <jakub@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Peter Johansson <trojkan@gmail.com>,
Zack Weinberg <zack@owlfolio.org>, Autoconf <autoconf@gnu.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: configure adds -std=gnu++11 to CXX variable
Date: Tue, 28 May 2024 09:20:10 +0100 [thread overview]
Message-ID: <CAH6eHdQ=ZSWC158e4enN9=WgLbgDAn6A5rGtRVDoE5WvcvyZbg@mail.gmail.com> (raw)
In-Reply-To: <25aee7da-bdd5-4a2a-b6ac-fa1a4aa11cc7@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On Tue, 28 May 2024, 02:51 Paul Eggert, <eggert@cs.ucla.edu> wrote:
> On 2024-05-27 12:18, Jakub Jelinek wrote:
> > Maybe respect the carefully chosen compiler default (unless explicitly
> > overridden in configure.ac)?
>
> Autoconf gave up on that idea long ago, as we had bad experiences with
> compiler defaults being chosen for the convenience of distro maintainers
> rather than for application developers and builders. Compilers were
> still defaulting to K&R long after that made little sense.
What has that got to do with C++ dialects?
GCC defaults to C++17 in versions that have good, stable C++17 support. So
does Clang these days. So what problem are you trying to solve for C++ here?
It was a bit
> like what we're still experiencing with _FILE_OFFSET_BITS defaulting to
> 32 on x86 GNU/Linux.
>
> Using the compiler default puts you at the mercy of the distro. It's not
> always wrong to do that - which is why developers and builders should
> have an option - but it's not always right either.
>
I am not aware of any distro ever changing the default -std setting for g++
or clang++. Are you attempting to solve a non-problem, but introducing new
ones?
next prev parent reply other threads:[~2024-05-28 8:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEZXgxjf7fQNHvkA09ia8ivHEsOHVKhzvoqdq=TCNRfdFTJryA@mail.gmail.com>
[not found] ` <aece3efd-503b-4106-99ad-e66be8b0b684@app.fastmail.com>
[not found] ` <00dc6e30-2e12-4b29-951b-d600097b38d0@gmail.com>
[not found] ` <80bf1a5a-63a3-4da4-8721-88c760243add@cs.ucla.edu>
2024-05-27 10:35 ` Florian Weimer
2024-05-27 19:04 ` Paul Eggert
2024-05-27 19:18 ` Jakub Jelinek
2024-05-28 1:50 ` Paul Eggert
2024-05-28 8:20 ` Jonathan Wakely [this message]
2024-05-28 14:35 ` Paul Eggert
2024-05-28 15:01 ` Jason Merrill
2024-05-28 15:02 ` Jakub Jelinek
2024-05-28 16:44 ` Joseph Myers
2024-05-28 16:45 ` Paul Eggert
2024-05-28 18:27 ` Jason Merrill
2024-05-28 20:09 ` Paul Eggert
2024-05-29 17:33 ` Tom Tromey
2024-05-29 17:40 ` Jason Merrill
2024-05-28 6:23 ` Florian Weimer
2024-05-28 8:15 ` 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='CAH6eHdQ=ZSWC158e4enN9=WgLbgDAn6A5rGtRVDoE5WvcvyZbg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=autoconf@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=trojkan@gmail.com \
--cc=zack@owlfolio.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).