This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Add missing INCLUDE_DEFAULTS_MUSL_LOCAL
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- Cc: Doug Evans <dje at google dot com>, Bernd Schmidt <bschmidt at redhat dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>, Kyrill Tkachov <kyrylo dot tkachov at arm dot com>, Rich Felker <dalias at libc dot org>
- Date: Mon, 26 Oct 2015 23:39:31 +0000
- Subject: Re: [PATCH] Add missing INCLUDE_DEFAULTS_MUSL_LOCAL
- Authentication-results: sourceware.org; auth=none
- References: <047d7b6d8c8c4d13600522a1ffa5 at google dot com> <562A697E dot 5040608 at redhat dot com> <CADPb22SqEK0ZgHwMD4bBM8B60xyOeSFCW8nvguD+zXandEXQgw at mail dot gmail dot com> <562A7DBC dot 1060400 at arm dot com> <alpine dot DEB dot 2 dot 10 dot 1510232012140 dot 5421 at digraph dot polyomino dot org dot uk> <562E1D41 dot 2040504 at arm dot com>
On Mon, 26 Oct 2015, Szabolcs Nagy wrote:
> > FLT_ROUNDS is an ordinary compiler bug (bug 30569), should be fixable
> > reasonably straightforwardly as outlined at
> > <https://gcc.gnu.org/ml/gcc/2013-11/msg00317.html>, probably within say a
> > week's work if most architecture-specific changes are left to architecture
> > maintainers.
>
> musl tries to support old compilers in general (it can be built
> with gcc 3.x, and it should be possible to use with a wider range
> of compilers with reasonably consistent semantics, so fixing that
> bug in gcc does not help much.)
Well, the general expectation in the GNU system is that GCC and glibc may
work around each other's issues if the one doing the working around is
responsible for the interface that needs the workaround - but also that
interfaces required for freestanding implementations are GCC's
responsibility while interfaces involving library functions are the C
library's responsibility. GCC fixincludes doesn't try to fix library
issues not relevant for GCC and its tests unless they actually break use
of a header with GCC, and glibc doesn't try to fix issues with headers
provided by GCC.
(There may be the odd deviation from that starting point - GCC provides
stdatomic.h because it's so closely linked to the compiler despite not
being required of freestanding implementations, and GCC would not start to
provide libm in future if adopting TS 18661-1 despite it requiring more
library functionality for freestanding implementations.)
--
Joseph S. Myers
joseph@codesourcery.com