This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/2] BZ#13743: PowerPC - Add a new header for platformspecific functions
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, ryan dot arnold at gmail dot com, libc-alpha at sourceware dot org, sjmunroe at us dot ibm dot com
- Date: Tue, 6 Mar 2012 09:25:48 -0800 (PST)
- Subject: Re: [PATCH 1/2] BZ#13743: PowerPC - Add a new header for platformspecific functions
- References: <20120224164824.GB3455@linux.vnet.ibm.com><1331042262-25221-1-git-send-email-tuliom@linux.vnet.ibm.com><CADZpyix82sHSd-JDFUxd8PVHpXbjFG_2=iy2UZhFb8iz_C8rNA@mail.gmail.com>
> I would like to see sys/platform.h become the place for non-standard
> low-level macros.
The standard place for nonstandard interfaces. Sure, buddy. Whatever.
Given that they are entirely nonstandard anyway, I'm not sure it makes
much difference whether they are in some generic-sounding header like
this or in headers with more specific names.
I'm solidly ambivalent about the utility of a catch-all header for
random things. I'd say the fact that other systems use this file name
is between meaningless and negative as a recommendation to use it for
something that isn't even trying to be compatible with any other system.
In the absence of any common interface (which could even be just one
other system whose header name and interface we match, as we have done
before), there is some logic in using individual headers with names as
specific as possible (e.g. <ppc-timebase.h> here). That makes it much
clearer for applications to include exactly what they use.
Thanks,
Roland