On Mon, Sep 06, 2021 at 10:58:53AM +0200, Jakub Jelinek via Gcc-patches wrote:
> On Mon, Sep 06, 2021 at 08:49:27AM +0100, Iain Sandoe wrote:
> > > Ok.  The *.ver changes are still needed (see above), but that can be done
> > > incrementally.
> > 
> > I can commit the .ver change if that’s approved, sure - for the record I 
> > haven’t checked
> > any targets other than Darwin and Linux.
> 
> The following patch exports it for Linux from config/i386/*.ver where it
> IMNSHO belongs, aarch64 already exports some of those at GCC_11* and other
> targets might add them at completely different gcc versions.
> 
> Tested on x86_64-linux, verified the right symbols are exported, ok for trunk?

Bootstrapped/regtested on x86_64-linux and i686-linux successfully, though
actually __divhc3 and __mulhc3 aren't exported, they aren't even compiled
into libgcc_s.so.1.  Is that on purpose (large functions very unlikely being
used in most of the programs)?  If yes, I'll drop the __divhc3/__mulhc3
lines.  If not,
LIB2ADD_ST += $(addprefix $(srcdir)/config/i386/, $(libgcc2-hf-extras))
should be changed to
LIB2ADD += $(addprefix $(srcdir)/config/i386/, $(libgcc2-hf-extras))
(untested), or even the LIB2FUNCS_EXCLUDE dropped?

> 2021-09-06  Jakub Jelinek  <ja...@redhat.com>
>           Iain Sandoe  <i...@sandoe.co.uk>
> 
>       * config/i386/libgcc-glibc.ver: Add %inherit GCC_12.0.0 GCC_7.0.0
>       and export *hf* and *hc* functions at GCC_12.0.0.
> 
> --- libgcc/config/i386/libgcc-glibc.ver.jj    2021-01-05 00:13:58.142298913 
> +0100
> +++ libgcc/config/i386/libgcc-glibc.ver       2021-09-06 10:47:52.244726676 
> +0200
> @@ -194,3 +194,23 @@ GCC_4.8.0 {
>    __cpu_indicator_init
>  }
>  %endif
> +
> +%inherit GCC_12.0.0 GCC_7.0.0
> +GCC_12.0.0 {
> +  __divhc3
> +  __mulhc3
> +  __eqhf2
> +  __nehf2
> +  __extendhfdf2
> +  __extendhfsf2
> +  __extendhftf2
> +  __extendhfxf2
> +  __fixhfti
> +  __fixunshfti
> +  __floattihf
> +  __floatuntihf
> +  __truncdfhf2
> +  __truncsfhf2
> +  __trunctfhf2
> +  __truncxfhf2
> +}

        Jakub

Reply via email to