This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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: [RFC] time: Create a endian_t.h headerfile

From: Zack Weinberg <zackw at panix dot com>
To: Joseph Myers <joseph at codesourcery dot com>
Cc: Alistair Francis <alistair dot francis at wdc dot com>, GNU C Library <libc-alpha at sourceware dot org>
Date: Fri, 20 Sep 2019 11:20:49 -0400
Subject: Re: [RFC] time: Create a endian_t.h headerfile
References: <20190919221829.6137-1-alistair.francis@wdc.com> <alpine.DEB.2.21.1909192327000.11875@digraph.polyomino.org.uk>

On Thu, Sep 19, 2019 at 7:34 PM Joseph Myers <joseph@codesourcery.com> wrote:
>
> If anything, I think the cleanest naming would be to have <bits/endian.h>
> be the architecture-independent header that defines these three macros and
> includes <bits/endian-arch.h>, where the existing <bits/endian.h> headers
> that define __BYTE_ORDER all get renamed to <bits/endian-arch.h>.  So
> you'd need to add bits/endian-arch.h to the "headers" setting in
> string/Makefile.

I believe I wrote that patch already, in fact, as part of my
installed-headers cleanups series:
https://sourceware.org/ml/libc-alpha/2019-06/msg00783.html  Unlike a
lot of those patches, it should be low-risk for application breakage
and applicable independently.

zw

Follow-Ups:
- Re: [RFC] time: Create a endian_t.h headerfile
  - From: Joseph Myers

References:
- [RFC] time: Create a endian_t.h headerfile
  - From: Alistair Francis
- Re: [RFC] time: Create a endian_t.h headerfile
  - From: Joseph Myers

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