From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Krystian Kuźniarek" <krystian.kuzniarek@gmail.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
"libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: remove an ignored qualifier on function return type
Date: Thu, 29 Oct 2020 17:18:36 +0000 [thread overview]
Message-ID: <CAH6eHdQGCuA4TxMaEUTm2t1ZN_HDGNWtf69ukvE6Beq55ZOQmA@mail.gmail.com> (raw)
In-Reply-To: <CAHqJ0wHR53prcn-yniUWc3-VusygYWGWtbuOZu10i2hvzFMHPQ@mail.gmail.com>
On Fri, 28 Aug 2020 at 07:56, Krystian Kuźniarek via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> > So then you need to produce a changelog entry by hand.
> I had this problem on some old Ubuntu 18.04. Anyway, here's new ChangeLog:
>
> libstdc++-v3/ChangeLog:
>
> * include/std/variant: Fix -Wignored-qualifiers
> in system headers.
>
>
> >That doesn't test this header at all.
> It does but indirectly. What I meant by manual test was:
> ${GCC_GIT} -E contains_only_stdcpp_include.cpp > preprocessed.cpp
> ${GCC_GIT} -Wall -Wextra -pedantic -fsyntax-only preprocessed.cpp
> By manipulating GCC_GIT variable to trunk GCC and patched GCC, I checked if
> the warning is gone.
>
> >What about the libstdc++ testsuite?
> I hope you mean calling make bootstrap and make check. If that's ok, I
> confirm it works on Manjaro and Ubuntu 18.04 with gcc10 and gcc8
> respectively.
>
> >I don't remember exactly why I put it there, but I seem to recall it
> >was necessary.
> I don't know your reasons but I can only tell that this patch seems to
> compile and work just fine.
I see new test failures with that change:
include/variant:1039: error: invalid conversion from
'std::enable_if_t<true, const void> (*)(test02()::Visitor&&,
std::variant<int, double>&)' {aka 'void (*)(test02()::Visitor&&,
std::variant<int, double>&)'} to
'std::__detail::__variant::_Multi_array<co
nst void (*)(test02()::Visitor&&, std::variant<int,
double>&)>::__untag_result<const void (*)(test02()::Visitor&&,
std::variant<int, double>&)>::element_type' {aka 'const void
(*)(test02()::Visitor&&, std::variant<int, double>&)'} [-fpermissive]
UNRESOLVED: 20_util/variant/visit_r.cc compilation failed to produce executable
So I still think it's there for a reason.
next prev parent reply other threads:[~2020-10-29 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 11:26 Krystian Kuźniarek
2020-08-24 11:38 ` Jonathan Wakely
2020-08-28 6:55 ` Krystian Kuźniarek
2020-08-28 7:16 ` Krystian Kuźniarek
2020-10-29 17:18 ` Jonathan Wakely [this message]
2020-10-31 12:18 ` Krystian Kuźniarek
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=CAH6eHdQGCuA4TxMaEUTm2t1ZN_HDGNWtf69ukvE6Beq55ZOQmA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=krystian.kuzniarek@gmail.com \
--cc=libstdc++@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).