This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PING][PATCH 2/3] retire mem_signal_fence pattern
- From: Jeff Law <law at redhat dot com>
- To: Alexander Monakov <amonakov at ispras dot ru>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sun, 3 Sep 2017 22:55:25 -0600
- Subject: Re: [PING][PATCH 2/3] retire mem_signal_fence pattern
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=law at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 6B38E8046C
- References: <20170802174548.12344-1-amonakov@ispras.ru> <20170802174548.12344-2-amonakov@ispras.ru> <alpine.LNX.2.20.13.1708281408400.16251@monopod.intra.ispras.ru> <d738f0d1-e9d1-bfb2-e413-4d4b78370cdb@redhat.com> <alpine.LNX.2.20.13.1709010923330.21360@monopod.intra.ispras.ru>
On 09/01/2017 12:26 AM, Alexander Monakov wrote:
> On Thu, 31 Aug 2017, Jeff Law wrote:
>> This is OK.
>>
>> What's the point of the delete_insns_since calls in patch #3?
>
> Deleting the first barrier when maybe_expand_insn failed.
> Other functions in the file use a similar approach.
Thanks for clarifying. OK for the trunk. Sorry about the wait.
Jeff