This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] Make _FILE_OFFSET_BITS=64 default.
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>
- Cc: Mike Frysinger <vapier at gentoo dot org>, <libc-alpha at sourceware dot org>
- Date: Wed, 19 Mar 2014 18:46:43 +0000
- Subject: Re: [RFC] Make _FILE_OFFSET_BITS=64 default.
- Authentication-results: sourceware.org; auth=none
- References: <1393521776-1102-1-git-send-email-reprofy at etersoft dot ru> <3427802 dot 83HSs9lgGH at vapier> <532956D4 dot 5020804 at cs dot ucla dot edu> <9842031 dot PgVxWc0IpI at vapier> <5329DC42 dot 2000409 at cs dot ucla dot edu>
On Wed, 19 Mar 2014, Paul Eggert wrote:
> On 03/19/2014 02:14 AM, Mike Frysinger wrote:
> > i have gotten complaints in the past that glibc provided half-baked support
> > for static assert when building with <gcc-4.6. so this would make those
> > people happy too:).
> OK, I'm attaching the patch in more formal form, broken into two parts (one
> for _Static_assert, one for fts.h, the latter dependent on the former), for
> further review. I'd like to install it unless further objections turn up.
I don't think the installed glibc headers should be providing
_Static_assert (arguably assert.h should try to do something for the case
of _ISOC11_SOURCE, non-C11 compiler, as a quality-of-implementation
matter, but defining it for everything that includes any system header
seems much riskier). I certainly don't think they should be overriding
_Static_assert provided by GCC (>= 4.6) as an extension outside C11 mode
(but generally that applies to any compiler possibly providing
_Static_assert outside C11 mode - the library shouldn't get in the way of
the user using the compiler feature).
--
Joseph S. Myers
joseph@codesourcery.com