This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: libm -fno-builtin

From: "Jon Beniston" <jon at beniston dot com>
To: <newlib at sourceware dot org>
Date: Mon, 25 Jun 2018 14:26:18 +0100
Subject: RE: libm -fno-builtin
References: <005301d407c1$b3a9a8b0$1afcfa10$@beniston.com> <000501d408b1$5640d4f0$02c27ed0$@beniston.com> <20180621073037.GG11110@calimero.vinschen.de> <018c01d40a0d$6ab0a0c0$4011e240$@beniston.com> <20180625113109.GH28757@calimero.vinschen.de> <20180625113724.GI28757@calimero.vinschen.de> <017601d40c82$b0dd9360$1298ba20$@beniston.com>

>>Uhm... even more importantly, your patch is changing the configure files directly,
>> rather than changing the configure.in files the configure files are generated from.  
>>
>> For the patch, just change the configure.in files and send the below manual configure changes alongside
>
>-fno-builtin isn't in configure.in. Where does that come from?

It looks like it comes from a common acinclude.m4 that is shared with libc, where I presume -fno-builtin should still be used. Any ideas how that should be resolved? 

Cheers,
Jon

References:
- libm -fno-builtin
  - From: Jon Beniston
- RE: libm -fno-builtin
  - From: Jon Beniston
- Re: libm -fno-builtin
  - From: Corinna Vinschen
- RE: libm -fno-builtin
  - From: Jon Beniston
- Re: libm -fno-builtin
  - From: Corinna Vinschen
- Re: libm -fno-builtin
  - From: Corinna Vinschen
- RE: libm -fno-builtin
  - From: Jon Beniston

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]