On Fri, Nov 14, 2014 at 7:51 AM, Uros Bizjak wrote:
> On Fri, Nov 14, 2014 at 3:38 PM, H.J. Lu wrote:
>> On Thu, Nov 13, 2014 at 09:32:07PM -0800, H.J. Lu wrote:
>>> For i[34567]86-*-linux* and x86_64-*-linux* targets, config.gcc assumes
>>> modern glibc and set default_gnu_indirect_function to y
On Fri, Nov 14, 2014 at 3:38 PM, H.J. Lu wrote:
> On Thu, Nov 13, 2014 at 09:32:07PM -0800, H.J. Lu wrote:
>> For i[34567]86-*-linux* and x86_64-*-linux* targets, config.gcc assumes
>> modern glibc and set default_gnu_indirect_function to yes. That is wrong
>> for i[34567]86-*-linux-android* and
On Fri, Nov 14, 2014 at 7:10 AM, Alexander Ivchenko wrote:
> should we also change this comment in gcc/configure?
>
> --enable-gnu-indirect-function
> enable the use of the @gnu_indirect_function to
> glibc systems
That will be a separate issu
should we also change this comment in gcc/configure?
--enable-gnu-indirect-function
enable the use of the @gnu_indirect_function to
glibc systems
So, if the patch that I sent for removing linux_has_ifunc_p is
approved, we will just add "--en
On Thu, Nov 13, 2014 at 09:32:07PM -0800, H.J. Lu wrote:
> For i[34567]86-*-linux* and x86_64-*-linux* targets, config.gcc assumes
> modern glibc and set default_gnu_indirect_function to yes. That is wrong
> for i[34567]86-*-linux-android* and x86_64-*-linux-android* targets.
> This patch fixes it
