public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "maxim.yegorushkin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94184] New: Global variable inline constructor elision.
Date: Sun, 15 Mar 2020 19:36:21 +0000	[thread overview]
Message-ID: <bug-94184-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94184
           Summary: Global variable inline constructor elision.
           Product: gcc
           Version: 9.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: maxim.yegorushkin at gmail dot com
  Target Milestone: ---

The following code:

    struct A { 
        int a_; 
        A(int a) : a_(a) {}
    };

    struct B { 
        int a_; 
        constexpr B(int a) : a_(a) {}
    };

    A a{1};
    B b{1};

When compiled with `gcc-9.2 -O3 -march=skylake -mtune=skylake -std=gnu++17`
generates a call to `A` constructor for variable `a`:

    _GLOBAL__sub_I_a:
        mov    DWORD PTR [rip+0x200bd6],0x1        # 601030 <__TMC_END__>
        ret    

And no call for `B` constructor for variable `b`, as expected of `constexpr`.

`clang-9.0 -O3 -march=skylake -mtune=skylake -std=gnu++17`, however, elides the
constructor calls for both `a` and `b` global variables, regardless of
`constexpr`.

Why can't `gcc` elide the call to `A` constructor for `a`, since `A` constuctor
is an inline function with a clear side-effect?

https://gcc.godbolt.org/z/5y3cD5

             reply	other threads:[~2020-03-15 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 19:36 maxim.yegorushkin at gmail dot com [this message]
2020-03-15 19:52 ` [Bug c++/94184] " pinskia at gcc dot gnu.org
2022-10-17 13:40 ` trass3r at gmail dot com
2022-10-17 14:11 ` ppalka 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-94184-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).