Displaying 3 results from an estimated 3 matches for "setfeaturebit".
Did you mean:
setfeaturebits
2013 Nov 22
0
[LLVMdev] switching ARM modes and integrated-as
...hat const_cast? Also, the patch does not restore the TargetSubtargetInfo
to its original state. So if you changed from Thumb to ARM mode, but not
back to Thumb, the code emitter will generate broken machine code.
Unfortunately, the TargetSubtargetInfo class does not expose a copy
constructor or a setFeatureBits() method. Should it? Or should we expect
the inline assembly to be responsible for restoring the mode itself?
Thanks,
Greg
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
Behalf Of Greg Fitzgerald
Sent: Tuesday, November 19, 2013 11:07...
2013 Nov 19
3
[LLVMdev] switching ARM modes and integrated-as
> I just tried the above code in a .s file and it worked fine for me.
> Can you show exactly what you’re seeing that looks wrong?
Thanks Jim. I can only reproduce the issue when that code is inline
assembly in a bitcode file. Attached is a bitcode file and Makefile
to demonstrate. Calling 'make' will dump two object files 'c.o' and
'asm.o'. The former is created
2013 Nov 22
0
[LLVMdev] switching ARM modes and integrated-as
...o, the patch does not restore the TargetSubtargetInfo
> to its original state. So if you changed from Thumb to ARM mode, but not
> back to Thumb, the code emitter will generate broken machine code.
> Unfortunately, the TargetSubtargetInfo class does not expose a copy
> constructor or a setFeatureBits() method. Should it? Or should we expect
> the inline assembly to be responsible for restoring the mode itself?
>
> Thanks,
> Greg
>
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
> Behalf Of Greg Fitzgerald...