This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH GCC]Fix test case failure reported in PR54989

From: Jeff Law <law at redhat dot com>
To: Bin Cheng <bin dot cheng at arm dot com>
Cc: "'Jakub Jelinek'" <jakub at redhat dot com>, gcc-patches at gcc dot gnu dot org
Date: Mon, 29 Oct 2012 12:26:33 -0600
Subject: Re: [PATCH GCC]Fix test case failure reported in PR54989
References: <001d01cdb001$59be9310$0d3bb930$@cheng@arm.com> <20121022071546.GA1752@tucnak.redhat.com> <002101cdb02d$5a6ca960$0f45fc20$@cheng@arm.com> <508ADC41.6030206@redhat.com> <003b01cdb3f9$9a710860$cf531920$@cheng@arm.com>

On 10/26/2012 10:14 PM, Bin Cheng wrote:

Actually I am going to submit a patch monitoring the change of register
pressure accurately as we discussed before. With that patch, expressions
will be hoisted anyway if it can decrease register pressure thus this test
case won't fail anymore. So I am wondering whether I should check in this
patch or just waiting for that patch to fix this failure?
What's your opinion?

I'd go ahead and get in the fix for this failure as we would prefer as few unexpected failures as possible.

jeff

Follow-Ups:
- RE: [PATCH GCC]Fix test case failure reported in PR54989
  - From: Bin Cheng

References:
- [PATCH GCC]Fix test case failure reported in PR54989
  - From: Bin Cheng
- Re: [PATCH GCC]Fix test case failure reported in PR54989
  - From: Jakub Jelinek
- RE: [PATCH GCC]Fix test case failure reported in PR54989
  - From: Bin Cheng
- Re: [PATCH GCC]Fix test case failure reported in PR54989
  - From: Jeff Law
- RE: [PATCH GCC]Fix test case failure reported in PR54989
  - From: Bin Cheng

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]