public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, janis187@us.ibm.com, nobody@gcc.gnu.org Subject: Re: target/6137: ia64 -O3 generates bad overlapping memory accesses Date: Fri, 12 Apr 2002 17:37:00 -0000 [thread overview] Message-ID: <20020413003745.11543.qmail@sources.redhat.com> (raw) Synopsis: ia64 -O3 generates bad overlapping memory accesses State-Changed-From-To: open->analyzed State-Changed-By: rth State-Changed-When: Fri Apr 12 17:37:44 2002 State-Changed-Why: It's another damned RTX_UNCHANGING_P bug. (insn 85 84 88 (set (reg/v/f:DI 361) (plus:DI (reg/f:DI 328 sfp) (const_int 48 [0x30]))) 90 {adddi3} (nil) (nil)) (insn 98 97 99 (set (mem/s:DI (reg/v/f:DI 361) [0 S8 A64]) (reg:DI 365)) 6 {*movdi_internal} (nil) (nil)) (insn 133 131 134 (set (reg:DI 375) (mem/s/u:DI (reg/v/f:DI 361) [0 S8 A128])) 6 {*movdi_internal} (nil) (nil)) The load doesn't conflict with the store. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6137
next reply other threads:[~2002-04-13 0:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-12 17:37 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-10 9:41 janis 2002-04-02 10:46 janis187
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=20020413003745.11543.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=janis187@us.ibm.com \ --cc=nobody@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).