From: "François Dumont" <frs.dumont@gmail.com>
To: Ville Voutilainen <ville.voutilainen@gmail.com>,
Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR libstdc++/81064 fix versioned namespace
Date: Wed, 19 Jul 2017 21:02:00 -0000 [thread overview]
Message-ID: <75bbafbe-fb30-c356-5f08-0c467cc2d4df@gmail.com> (raw)
In-Reply-To: <CAFk2RUY_as20aKn_2+v3Q_ohtQ3uHF6mCbHURbjGTHoFOAU0uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
Here is the revisited version passing all tests successfully except 2
that are also failing without the patch:
FAIL: 21_strings/basic_string/modifiers/insert/char/1.cc execution test
FAIL: 21_strings/basic_string/modifiers/insert/wchar_t/1.cc execution test
This is a rather mechanical change except for few files I would like to
comment on:
- include/bits/c++config
I removed many declaration of namespace that are not necessary as
we don't need to declare any nested inline namespace anymore. In this
last version I managed to isolate the versioned namespace value to a
single location: the definition of _GLIBCXX_BEGIN_VERSION_NAMESPACE.
After the patch it is the only location of this version information so
next bump will be resume to updating c++config apart from python and
build scripts.
Note that the PR seems to say that the namespace should be always
declared the same way. In this patch __8 is declared inline only in
c++config, _GLIBCXX_BEGIN_VERSION_NAMESPACE don't repeat the inline keyword.
- include/bits/regex.h
- include/std/variant
In those 2 files we were having:
friend bool __detail::
#if _GLIBCXX_INLINE_VERSION
__8:: // Required due to PR c++/59256
#endif
...
I don't know if the front end change was to fix c++/59256 or if it
is due to the new namespace organization but I removed this code and
tests are successful. They were of course failing because there is no
more __detail::__8.
I am now ready to commit. I'll do it this week-end if I have no
further feedback.
François
[-- Attachment #2: versioned_namespace.patch.bz2 --]
[-- Type: application/x-bzip, Size: 19802 bytes --]
prev parent reply other threads:[~2017-07-19 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 20:55 François Dumont
2017-07-18 13:31 ` Jonathan Wakely
2017-07-18 13:31 ` Jonathan Wakely
2017-07-18 14:03 ` Ville Voutilainen
2017-07-18 19:17 ` François Dumont
2017-07-19 21:02 ` François Dumont [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=75bbafbe-fb30-c356-5f08-0c467cc2d4df@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=ville.voutilainen@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).