On 9 September 2011 18:04, Ulrich Weigand <uweig...@de.ibm.com> wrote: > > In theory, LEGITIMIZE_RELOAD_ADDRESS could attempt to handle them by > substituting the equivalent constant and then reloading the result. > However, this might need additional steps (pushing to the constant pool, > reloading the constant pool address, ...) which would lead to significant > duplication of code from core reload. This doesn't seem worthwhile > at this point ...
Thinking about it a bit more after our conversation, we do have the movw / movt instructions for armv7-a - why push this to the constant pool if we can rematerialize it ? Finding a way to use them rather than pushing things out to the constant pool might be an interesting experiment for later .. Could you let me know what configuration this was tested with ( i.e. the arch. flags ? ) and make sure this also ran through a run with the v7-a / softfp /neon configurations ? Regarding the testcase - please add an -mfloat-abi=soft to the testcase so that it tests the specific case that failed in case the default configuration was with softfp. cheers Ramana
