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 target/104723] [12 regression] Redundant usage of stack
Date: Tue, 01 Mar 2022 13:41:18 +0000	[thread overview]
Message-ID: <bug-104723-4-rtOiDwVB0X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104723-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2022-03-01
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |missed-optimization,
                   |                            |needs-bisection
   Target Milestone|---                         |12.0

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed with -O2 -march=skylake-avx512.  On the high-level side we fail to
promote write-once vars to static storage:

bool f256 (char * a)
{
  char t[49];

  <bb 2> [local count: 1073741824]:
  t = "012345678901234567890123456789012345678901234567";
  __builtin_memcpy (a_3(D), &t[0], 49);
  t ={v} {CLOBBER};
  return 0;

}

  parent reply	other threads:[~2022-03-01 13:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  8:35 [Bug target/104723] New: " crazylht at gmail dot com
2022-03-01  8:44 ` [Bug target/104723] " crazylht at gmail dot com
2022-03-01  8:47 ` crazylht at gmail dot com
2022-03-01 12:38 ` lili.cui at intel dot com
2022-03-01 13:41 ` rguenth at gcc dot gnu.org [this message]
2022-03-01 16:00 ` jakub at gcc dot gnu.org
2022-03-01 16:07 ` jakub at gcc dot gnu.org
2022-03-01 18:45 ` hjl.tools at gmail dot com
2022-03-01 18:50 ` hjl.tools at gmail dot com
2022-03-02  8:11 ` lili.cui at intel dot com
2022-04-22 16:28 ` jakub at gcc dot gnu.org
2022-04-24  7:37 ` lili.cui at intel dot com
2022-04-26  9:41 ` jakub at gcc dot gnu.org
2022-05-06  8:32 ` [Bug target/104723] [12/13 " jakub at gcc dot gnu.org
2022-07-26 12:58 ` rguenth at gcc dot gnu.org
2023-05-08 12:23 ` [Bug target/104723] [12/13/14 " 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-104723-4-rtOiDwVB0X@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).