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][M68K] Fix extendsidi pattern to handle ColdFire


Maxim Kuvyrkov wrote:

but in the rm->d case you end up allocating an unnecessary scratch register.

But why? In rm->d case the constraints in the (match_scratch)'es are 'X', so the RA/reload should not assign anything meaningful to them. Or am I misinterpreting GCC Internals?
So why bother with operand3 at all as all its alternatives are 'X'?

Jeff


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