public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/31677] gcc.dg/memcpy-1.c tree dump scan fails on several targets Date: Mon, 23 Apr 2007 23:30:00 -0000 [thread overview] Message-ID: <20070423233041.7909.qmail@sourceware.org> (raw) In-Reply-To: <bug-31677-4503@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2007-04-24 00:30 ------- A couple of issues here: nasty_local.a = nasty_local$a; is a SRA issue and that should not be needed. The rest is just SRA not doing element copy for the struct (it is not a big issue) and the testcase should just include "--param sra-max-structure-size=32" because what it is testing is that SRA can do the element copy with the removal of memcpy. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-04-24 00:30:40 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31677
next prev parent reply other threads:[~2007-04-23 23:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-23 23:25 [Bug tree-optimization/31677] New: " janis at gcc dot gnu dot org 2007-04-23 23:30 ` pinskia at gcc dot gnu dot org [this message] 2008-12-02 22:30 ` [Bug tree-optimization/31677] " janis at gcc dot gnu dot org 2009-02-21 1:32 ` howarth at nitro dot med dot uc dot edu 2009-04-02 18:09 ` janis at gcc dot gnu dot org [not found] <bug-31677-4@http.gcc.gnu.org/bugzilla/> 2012-06-06 9:59 ` 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=20070423233041.7909.qmail@sourceware.org \ --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).