From: Patrick Palka <ppalka@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [pushed] c++: fix tourney logic
Date: Fri, 27 Oct 2023 16:34:29 -0400 (EDT) [thread overview]
Message-ID: <c8a13e3b-2dd8-0eb5-1df0-b83991a78e99@idea> (raw)
In-Reply-To: <ca79b85f-00aa-07c0-1716-06a6728b9ad3@idea>
On Fri, 27 Oct 2023, Patrick Palka wrote:
> On Fri, 27 Oct 2023, Patrick Palka wrote:
>
> > On Fri, 20 Oct 2023, Jason Merrill wrote:
> >
> > > Tested x86_64-pc-linux-gnu, applying to trunk. Patrick, sorry I didn't apply
> > > this sooner.
> > >
> > > -- 8< --
> > >
> > > In r13-3766 I changed the logic at the end of tourney to avoid redundant
> > > comparisons, but the change also meant skipping any less-good matches
> > > between the champ_compared_to_predecessor candidate and champ itself.
> > >
> > > This should not be a correctness issue, since we believe that joust is a
> > > partial order. But it can lead to missed warnings, as in this testcase.
> >
> > I suppose this rules out optimizing tourney via transitivity when in
> > a non-SFINAE context since it'd cause missed warnings such as these.
> > But maybe we'd still want to optimize the second pass via transitivity
> > in a SFINAE context?
>
> Eh, maybe it's not worth it either way.. According to some quick
> experiments, making the second pass in tourney assume transitivity by
> going up to the most recent tie even in non-SFINAE contexts reduces the
> total number of non-trivial calls to tourney by about 5%. Doing the
total number of non-trivial calls to joust, rather
> same in only SFINAE contexts reduces the number of calls by less than 1%.
>
> >
> > >
> > > gcc/cp/ChangeLog:
> > >
> > > * call.cc (tourney): Only skip champ_compared_to_predecessor.
> > >
> > > gcc/testsuite/ChangeLog:
> > >
> > > * g++.dg/warn/Wsign-promo1.C: New test.
> > > ---
> > > gcc/cp/call.cc | 5 +++--
> > > gcc/testsuite/g++.dg/warn/Wsign-promo1.C | 15 +++++++++++++++
> > > 2 files changed, 18 insertions(+), 2 deletions(-)
> > > create mode 100644 gcc/testsuite/g++.dg/warn/Wsign-promo1.C
> > >
> > > diff --git a/gcc/cp/call.cc b/gcc/cp/call.cc
> > > index 657eca93d23..a49fde949d5 100644
> > > --- a/gcc/cp/call.cc
> > > +++ b/gcc/cp/call.cc
> > > @@ -13227,10 +13227,11 @@ tourney (struct z_candidate *candidates, tsubst_flags_t complain)
> > > been compared to. */
> > >
> > > for (challenger = candidates;
> > > - challenger != champ
> > > - && challenger != champ_compared_to_predecessor;
> > > + challenger != champ;
> > > challenger = challenger->next)
> > > {
> > > + if (challenger == champ_compared_to_predecessor)
> > > + continue;
> > > fate = joust (champ, challenger, 0, complain);
> > > if (fate != 1)
> > > return NULL;
> > > diff --git a/gcc/testsuite/g++.dg/warn/Wsign-promo1.C b/gcc/testsuite/g++.dg/warn/Wsign-promo1.C
> > > new file mode 100644
> > > index 00000000000..51b76eee735
> > > --- /dev/null
> > > +++ b/gcc/testsuite/g++.dg/warn/Wsign-promo1.C
> > > @@ -0,0 +1,15 @@
> > > +// Check that we get joust warnings from comparing the final champ to a
> > > +// candidate between it and the previous champ.
> > > +
> > > +// { dg-additional-options -Wsign-promo }
> > > +
> > > +struct A { A(int); };
> > > +
> > > +enum E { e };
> > > +
> > > +int f(int, A);
> > > +int f(unsigned, A);
> > > +int f(int, int);
> > > +
> > > +int i = f(e, 42); // { dg-warning "passing 'E'" }
> > > +// { dg-warning "in call to 'int f" "" { target *-*-* } .-1 }
> > >
> > > base-commit: 084addf8a700fab9222d4127ab8524920d0ca481
> > > --
> > > 2.39.3
> > >
> > >
> >
>
prev parent reply other threads:[~2023-10-27 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 20:29 Jason Merrill
2023-10-27 20:22 ` Patrick Palka
2023-10-27 20:33 ` Patrick Palka
2023-10-27 20:34 ` Patrick Palka [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=c8a13e3b-2dd8-0eb5-1df0-b83991a78e99@idea \
--to=ppalka@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).