Re: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0

2012-05-03 Thread Ulrich Weigand
Bin Cheng wrote: Thanks for reviewing, I modified the ChangeLog. Is it ok for trunk and 4.7? Yes, this is OK for trunk. Once it has been in trunk for a week or so and nobody reported any regressions, it would also be OK to backport to 4.7. Thanks, Ulrich -- Dr. Ulrich Weigand GNU

RE: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0

2012-05-03 Thread Bin Cheng
-Original Message- From: Ulrich Weigand [mailto:uweig...@de.ibm.com] Sent: Thursday, May 03, 2012 6:11 PM To: Bin Cheng Cc: gcc-patches@gcc.gnu.org Subject: Re: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0 Bin Cheng wrote: Thanks

RE: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0

2012-05-02 Thread Bin Cheng
Ping. Hi, could anyone help me with this bug please, if you have time? Any comments will be appreciated. Thanks very much. -Original Message- From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org] On Behalf Of Bin Cheng Sent: Friday, April 20, 2012 1:51 PM To:

Re: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0

2012-05-02 Thread Ulrich Weigand
Bin Cheng wrote: In short, I think the confliction of reloads with type RELOAD_FOR_INPADDR_ADDRESS and type RELOAD_FOR_INPUT_ADDRESS should be handled in reload_reg_reaches_end_p. Also I think RELOAD_FOR_OUTPUT_ADDRESS/RELOAD_FOR_OUTADDR_ADDRESS have the issue symmetrically, though I have

RE: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0

2012-05-02 Thread Bin Cheng
-Original Message- From: Ulrich Weigand [mailto:uweig...@de.ibm.com] Sent: Thursday, May 03, 2012 12:05 AM To: Bin Cheng Cc: gcc-patches@gcc.gnu.org Subject: Re: [PATCH, reload] Fix bug pr52804, RELOAD pass reloads wrong register on ARM for cortex-m0 Bin Cheng wrote