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/63483] Scheduler performs Invalid move of aliased memory reference
Date: Wed, 08 Oct 2014 10:49:00 -0000 [thread overview]
Message-ID: <bug-63483-4-rXfSxCsmMS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63483-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63483
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |alpha
Component|rtl-optimization |target
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
The bug is clearly in
"
> Btw, if the mem is MEM_READONLY_P how can it be part of
> a {un}aligned_store sequence?
This flag is copied from the original memory operand of the store by
alpha_set_memflags to all memory operands in the expanded sequence."
and thus should be fixed there. What is the "original" memory reference
here? It seems for the read-modify-write you should use the target MEM
but somehow a source MEM gets used? Or rather you should not use either
MEMs flags for _all_ MEMs in the sequence but properly distinguish between
MEMs generated for the load of the source and MEMs generated for the store
to the destination.
next prev parent reply other threads:[~2014-10-08 10:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 8:26 [Bug rtl-optimization/63483] New: " ubizjak at gmail dot com
2014-10-08 8:34 ` [Bug rtl-optimization/63483] " ubizjak at gmail dot com
2014-10-08 9:05 ` ubizjak at gmail dot com
2014-10-08 10:49 ` rguenth at gcc dot gnu.org [this message]
2014-10-08 11:43 ` [Bug target/63483] " ubizjak at gmail dot com
2014-10-08 14:16 ` rguenth at gcc dot gnu.org
2014-10-08 14:20 ` rguenth at gcc dot gnu.org
2014-10-08 14:29 ` rguenth at gcc dot gnu.org
2014-10-08 15:30 ` ubizjak at gmail dot com
2014-10-09 12:40 ` ubizjak at gmail dot com
2014-10-09 12:54 ` rguenther at suse dot de
2014-10-09 13:11 ` ubizjak at gmail dot com
2014-10-10 7:06 ` rguenther at suse dot de
2014-10-10 9:51 ` ubizjak at gmail dot com
2014-10-10 17:36 ` uros at gcc dot gnu.org
2014-11-05 12:02 ` uros at gcc dot gnu.org
2014-11-05 12:16 ` ubizjak at gmail dot com
2015-02-20 12:05 ` uros 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-63483-4-rXfSxCsmMS@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).