Re: Fwd: [PATCH] Don't force-enable ifuncs on RISC-V

On 7/18/24 12:25 PM, Jeff Law wrote: On 7/18/24 4:09 AM, Maxim Blinov wrote: Let the user turn off ifunc support at configure time if they want to. Currently, the logic in gcc/autoconf.ac will override the default logic in gcc/config.gcc. gcc/ChangeLog: * config.gcc: Default-enable i

Re: Fwd: [PATCH] Don't force-enable ifuncs on RISC-V

On 7/18/24 4:09 AM, Maxim Blinov wrote: Let the user turn off ifunc support at configure time if they want to. Currently, the logic in gcc/autoconf.ac will override the default logic in gcc/config.gcc. gcc/ChangeLog: * config.gcc: Default-enable ifunc support for RISC-V on Linux. *

Re: Fwd: [PATCH] Don't force-enable ifuncs on RISC-V

On Jul 18 2024, Maxim Blinov wrote: > +if test $default_gnu_indirect_function = yes; then > + case "${target}" in > +riscv*-*-linux*) > + AC_MSG_CHECKING(linker ifunc IRELATIVE support) > + cat > conftest.s < + .text > + .typefoo_resolver, @function > + foo_resolver:

Fwd: [PATCH] Don't force-enable ifuncs on RISC-V

Let the user turn off ifunc support at configure time if they want to. Currently, the logic in gcc/autoconf.ac will override the default logic in gcc/config.gcc. gcc/ChangeLog: * config.gcc: Default-enable ifunc support for RISC-V on Linux. * autoconf.ac: Honor the default_gnu_indirect_fu