Fix sysdeps/unix/sysv/linux/arm/libc-do-syscall.S warning

Mike Frysinger vapier@gentoo.org
Sat Mar 14 07:54:00 GMT 2015


On 06 Mar 2015 22:15, Joseph Myers wrote:
> On Fri, 6 Mar 2015, Carlos O'Donell wrote:
> > I agree. My point is that we should do what's right for glibc first.
> > If there are two ways to fix this in glibc, and one way involves modifying
> > any assembly that includes the header, and the other solves the problem
> > once, then the changes to header are a better solution, for glibc, in my
> > opinion. This doesn't take into account any user requirements to include
> > the header in assembly files.
> 
> What about arranging for the configured CFLAGS to be used when building .S 
> files, so that -O options are active and the warning is avoided that way?  
> A comment in Makeconfig notes how -std=* can't be used for .S files, but 
> the -O options ought to work for them.

if we're going that route, what about adding -U_FORTIFY_SOURCE to ASFLAGS at 
configure time ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20150314/e68e4f44/attachment.sig>


More information about the Libc-alpha mailing list