This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Fix "conflicting types for built-in function" warnings fromnldbl-*.c
- From: David Miller <davem at davemloft dot net>
- To: joseph at codesourcery dot com
- Cc: libc-alpha at sourceware dot org, ryan dot arnold at gmail dot com
- Date: Tue, 04 Dec 2012 13:10:38 -0500 (EST)
- Subject: Re: Fix "conflicting types for built-in function" warnings fromnldbl-*.c
- References: <Pine.LNX.4.64.1212041544570.10522@digraph.polyomino.org.uk>
From: "Joseph S. Myers" <joseph@codesourcery.com>
Date: Tue, 4 Dec 2012 15:46:31 +0000
> Building for powerpc32, and probably other systems using ldbl-opt
> (i.e. supporting -mlong-double-64, now defaulting to
> -mlong-double-128, where a previous version only supported
> -mlong-double-64), produces many "conflicting types for built-in
> function" warnings building the nldbl-*.c compatibility functions for
> code using -mlong-double-64 (the code is using the type "double" in
> defining the versions of the long double functions that just wrap the
> functions for double). This patch fixes this by using the appropriate
> -fno-builtin-<function> option or options for each affected source
> file, to disable the conflicting built-in declaration.
>
> (There are still quite a few warnings left for powerpc32 after this
> patch ... I hope the architecture maintainers will also look at them
> for 2.17, and that they will look at cleaning up warnings for
> powerpc64 as well.)
I see the same warnings on 32-bit Sparc, as you had guessed.
I'm fine with this change.