This is the mail archive of the gcc@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]

Seeking suggestion


Suppose you're writing the backend for a VM supporting two architectures, in which
one of them clobbers the CC registers for certain instructions, while the other does not.
The instructions themselves are exactly the same.
What is the best/shortest/more-elegant way to write this, possibly w/out duplicating the
instructions?
I know I can write a define_expand and redirect, based on the TARGET, to two different
instructions (one with "clobber", the other w/out), but that's basically three declarations
for each insns. Is there a shorter way?


 - Jamie



      


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