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 d/103040] [12 Regression] gdc.dg/torture/pr101273.d FAILs
Date: Tue, 02 Nov 2021 19:39:20 +0000	[thread overview]
Message-ID: <bug-103040-4-NeAfWEMNJ0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103040-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #11)
> Sorry for the breakage.
> 
> Looking at Jakub's comment:
>   SR.11_24 = 0;
>   _12 = SR.11_24;
>   MEM <uint128_t> [(unsigned char * {ref-all})&nrvo] = _12;
>   nrvo = nrvo101273 (); [return slot optimization]
> instead of C++
>   nrvo = nrvo101273 (); [return slot optimization]
> 
> I think this may be the problem - we represent the call as full write and
> thus we do not expect
>   MEM <uint128_t> [(unsigned char * {ref-all})&nrvo] = _12;
> to survive.  We also do not expect the return slot argument to be read from
> - it should be write only and the write should correspond to the size of
> structure being initialized.

See above comments from Iain, even if that pre-initialization is removed it is
still miscompiled.  And, the testcase fails not because of the padding bits not
being zero, but because the address of self stored into one of the fields isn't
there or modref thinks it can't be changed or set to that.  But for
corresponding C++ it handles it ok.

  parent reply	other threads:[~2021-11-02 19:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  9:24 [Bug d/103040] New: " ro at gcc dot gnu.org
2021-11-02  9:24 ` [Bug d/103040] " ro at gcc dot gnu.org
2021-11-02  9:51 ` jakub at gcc dot gnu.org
2021-11-02 10:13 ` jakub at gcc dot gnu.org
2021-11-02 10:29 ` ibuclaw at gdcproject dot org
2021-11-02 10:31 ` jakub at gcc dot gnu.org
2021-11-02 10:44 ` jakub at gcc dot gnu.org
2021-11-02 10:46 ` jakub at gcc dot gnu.org
2021-11-02 11:15 ` ibuclaw at gdcproject dot org
2021-11-02 12:14 ` ibuclaw at gdcproject dot org
2021-11-02 13:41 ` ibuclaw at gdcproject dot org
2021-11-02 14:41 ` ibuclaw at gdcproject dot org
2021-11-02 18:26 ` [Bug d/103040] [12 Regression] " hubicka at gcc dot gnu.org
2021-11-02 19:39 ` jakub at gcc dot gnu.org [this message]
2021-11-02 19:57   ` Jan Hubicka
2021-11-02 19:57 ` hubicka at kam dot mff.cuni.cz
2021-11-02 20:28 ` ibuclaw at gdcproject dot org
2021-11-02 20:45 ` ibuclaw at gdcproject dot org
2021-11-02 20:53   ` Jan Hubicka
2021-11-02 20:53 ` hubicka at kam dot mff.cuni.cz
2021-11-02 21:05 ` hubicka at kam dot mff.cuni.cz
2021-11-03  0:46 ` cvs-commit at gcc dot gnu.org
2021-11-03  8:12 ` marxin at gcc dot gnu.org
2021-11-03 11:36 ` ibuclaw at gdcproject dot org
2021-11-03 11:44 ` marxin 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-103040-4-NeAfWEMNJ0@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).