On Wed, Aug 5, 2015 at 2:12 AM, kugan kugan.vivekanandara...@linaro.org wrote:
You indeed need to use CONVERT_EXPR here, maybe you can elaborate
on the optimization issues.
2. for inline asm (a reduced test case that might not make much as a
stand alone test-case, but I ran into similar
You indeed need to use CONVERT_EXPR here, maybe you can elaborate
on the optimization issues.
2. for inline asm (a reduced test case that might not make much as a
stand alone test-case, but I ran into similar cases with valid programmes)
;; Function fn1 (fn1, funcdef_no=0, decl_uid=4220,
On Tue, Jun 2, 2015 at 1:14 AM, Kugan kugan.vivekanandara...@linaro.org wrote:
Sorry for replying so late...
On 08/05/15 22:48, Richard Biener wrote:
You compute which promotions are unsafe, like sources/sinks of memory
(I think you miss call arguments/return values and also asm operands
ping?
Thanks,
Kugan
On 02/06/15 09:14, Kugan wrote:
On 08/05/15 22:48, Richard Biener wrote:
You compute which promotions are unsafe, like sources/sinks of memory
(I think you miss call arguments/return values and also asm operands here).
But instead of simply marking those SSA names as
On 08/05/15 22:48, Richard Biener wrote:
You compute which promotions are unsafe, like sources/sinks of memory
(I think you miss call arguments/return values and also asm operands here).
But instead of simply marking those SSA names as not to be promoted
I'd instead split their life-ranges,
On Fri, May 1, 2015 at 6:41 AM, Kugan kugan.vivekanandara...@linaro.org wrote:
Thanks for the comments. Here is a prototype patch that implements a
type promotion pass. This pass records SSA variables that will have
values in higher bits (than the original type precision) if promoted and
uses
Thanks for the comments. Here is a prototype patch that implements a
type promotion pass. This pass records SSA variables that will have
values in higher bits (than the original type precision) if promoted and
uses this information in inserting appropriate truncations and
extensions. This
On Mon, Nov 10, 2014 at 12:29 AM, Kugan
kugan.vivekanandara...@linaro.org wrote:
Well - the best way would be to expose the target specifics to GIMPLE
at some point in the optimization pipeline. My guess would be that it's
appropriate after loop optimizations (but maybe before induction
Well - the best way would be to expose the target specifics to GIMPLE
at some point in the optimization pipeline. My guess would be that it's
appropriate after loop optimizations (but maybe before induction variable
optimization).
That is, have a pass that applies register promotion to
