public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107624] New: Wrong code with static operator ()
Date: Thu, 10 Nov 2022 21:42:35 +0000	[thread overview]
Message-ID: <bug-107624-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107624

            Bug ID: 107624
           Summary: Wrong code with static operator ()
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
  Target Milestone: ---

In:
struct S {
  static void operator() (int);
  static void baz (int);
};
S &foo (int);

void
bar ()
{
  foo (0) (0);
  foo (1).baz (1);
}
we transform the latter into *foo (1), S::baz (1), but the former into just
S::operator() (0) - the side-effects on the postfix-expression are gone.
Shouldn't we add that somewhere as COMPOUND_EXPR when we select a static
operator() (ditto for static operator[])?

             reply	other threads:[~2022-11-10 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 21:42 jakub at gcc dot gnu.org [this message]
2022-11-10 21:45 ` [Bug c++/107624] [c++23] " pinskia at gcc dot gnu.org
2022-11-16 13:44 ` cvs-commit at gcc dot gnu.org
2022-11-16 14:01 ` jakub at gcc dot gnu.org
2022-11-28 22:23 ` pinskia at gcc dot gnu.org

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=bug-107624-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).