public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110055] Dangling pointer warning inside std::vector on RISC-V
Date: Thu, 01 Jun 2023 00:07:32 +0000	[thread overview]
Message-ID: <bug-110055-4-lTy3SMeHtQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110055-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> >  C.0 ={v} {CLOBBER(eol)};
> 
> 
> Should never have been emitted from the gimplifier.
> 
> 
> Confirmed, I have not reduced the testcase yet.
> But I can also confirm it on aarch64-linux-gnu with -O3 -mstrict-align
> -fno-exceptions .

So what is happening is we emitting the clobber and then changing it to be a
static variable.

This part happens even for x86_64 though the memcpy here can be removed.


      C.0 = {CLOBBER(eol)};

  parent reply	other threads:[~2023-06-01  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 10:03 [Bug c++/110055] New: " spriteovo at gmail dot com
2023-05-31 10:05 ` [Bug c++/110055] " spriteovo at gmail dot com
2023-05-31 13:32 ` spriteovo at gmail dot com
2023-05-31 23:46 ` [Bug middle-end/110055] " pinskia at gcc dot gnu.org
2023-05-31 23:47 ` pinskia at gcc dot gnu.org
2023-06-01  0:07 ` pinskia at gcc dot gnu.org [this message]
2023-06-02  7:13 ` rguenth at gcc dot gnu.org
2023-06-02  7:25 ` rguenth at gcc dot gnu.org
2023-06-05 11:15 ` spriteovo at gmail dot com
2023-06-06  8:30 ` cvs-commit at gcc dot gnu.org
2023-06-06  8:41 ` [Bug middle-end/110055] [13 Regression] " rguenth at gcc dot gnu.org
2023-06-23 10:30 ` cvs-commit at gcc dot gnu.org
2023-06-23 10:30 ` rguenth 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-110055-4-lTy3SMeHtQ@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).