sunfishcode wrote:

> I see, so in practice the effect on LLVM is that you get a relocation at each 
> call_indirect site but we don't need this relocation of the wide encoding for 
> any particular reason.

LLVM is already emitting those relocations in the default "generic" CPU today. 
If that's an undesirable default, perhaps we should make LLVM not emit these 
relocations by default, even when the target CPU says it can. This is 
independent of Lime1 or this PR though.

> It seems like a lot of steps and complexity just to force some binary 
> decoders to support an otherwise unused feature.. but you think its worth the 
> effort?

I guessed that since the "generic" CPU is already out there forcing various 
binary decoders to support this feature, it wouldn't be controversial for 
"lime1" to do it too.

https://github.com/llvm/llvm-project/pull/117087
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to