This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH v2, RTL]: Fix PR 63483, Scheduler performs Invalid move of aliased memory reference
- From: Jeff Law <law at redhat dot com>
- To: Uros Bizjak <ubizjak at gmail dot com>
- Cc: Richard Biener <rguenther at suse dot de>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Richard Henderson <rth at redhat dot com>
- Date: Fri, 10 Oct 2014 11:44:08 -0600
- Subject: Re: [PATCH v2, RTL]: Fix PR 63483, Scheduler performs Invalid move of aliased memory reference
- Authentication-results: sourceware.org; auth=none
- References: <CAFULd4ZBp4fubCh6ByezoS9AfjQk2zwQ_SdmRfb4Keo2ob3saw at mail dot gmail dot com> <543816A6 dot 7070307 at redhat dot com> <CAFULd4aFJ0cnAZprGNK43JZhEwoWFxhYTSjrQ9zLZBWOH7EeSQ at mail dot gmail dot com>
On 10/10/14 11:39, Uros Bizjak wrote:
Do we have anything other than the ancient alphas that don't have byte
access and thus have to generate the RMW sequences? If it's just the
ancient alphas, I wouldn't bother.
No objection. In fact, after reading everything it's pretty obvious to me
that a /u MEM must be considered as potentially conflicting with writes that
are implemented as RMW sequences to deal with the lack of byte access
Thanks, I went ahead and commit the patch to SVN mainline. I wonder,
if they should be also committed to release branches?