public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/99751] [11 Regression] wrong code at -O1 Date: Wed, 24 Mar 2021 12:46:40 +0000 [thread overview] Message-ID: <bug-99751-4-AcLmjuLCQk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99751-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99751 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- parm 0 flags: nodirectescape void e (int * d) { int * * c.0_1; int * _2; <bb 2> : c.0_1 = c; _2 = b (d_4(D)); *c.0_1 = _2; return; is wrong, it does escape through the *c store. I suppose b (d) is "wrong" somehow, the escape through the return is not mentioned: parm 0 flags: direct noclobber noescape nodirectescape int * b (int * d) { <bb 2> : return d_1(D);
next prev parent reply other threads:[~2021-03-24 12:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-24 12:32 [Bug tree-optimization/99751] New: " zhendong.su at inf dot ethz.ch 2021-03-24 12:35 ` [Bug tree-optimization/99751] [11 Regression] " rguenth at gcc dot gnu.org 2021-03-24 12:37 ` rguenth at gcc dot gnu.org 2021-03-24 12:38 ` [Bug ipa/99751] " rguenth at gcc dot gnu.org 2021-03-24 12:38 ` jakub at gcc dot gnu.org 2021-03-24 12:46 ` rguenth at gcc dot gnu.org [this message] 2021-03-25 15:17 ` marxin at gcc dot gnu.org 2021-03-29 10:15 ` hubicka at gcc dot gnu.org 2021-03-29 10:59 ` hubicka at gcc dot gnu.org 2021-03-29 11:25 ` hubicka at gcc dot gnu.org 2021-03-29 18:12 ` hubicka at gcc dot gnu.org 2021-03-29 19:00 ` cvs-commit 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-99751-4-AcLmjuLCQk@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: linkBe 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).