Re: gas relocations for .uleb128

["M R Swami Reddy" <MR dot Swami dot Reddy at nsc dot com>]

Hi Yvan,

> > Is the ".uleb128" directive expression generate relocation?
> >     
>
> As far as I know, the answer is No, and it's a problem if
> you want to support c++ exceptions and relaxation (for instance ;-)).
>   
Yes, I am also facing the same issue as you mentioned above for cr16 target.

> What we've done in the SH backend, is to disable the leb128
> encoding (in the compiler) when relaxation is enable (a patch
> for the SH relaxation is under construction). However, I think that
> it would be better to add the "leb128 support" in the linker, to
> take benefits from both sides.
What I am thinking is: in gas, add .leb128 processing (ie target specific)
and include the relocs if needed (ie similar to .long directive processing).
Is this ok?

Thanks
Swami