From: Dwight Guth <dwight.guth@runtimeverification.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Dwight Guth <dwight.guth@runtimeverification.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH][BZ 17979][BZ 17721] Fix issues with sys/cdefs.h and uchar.h when using non-gcc compiler.
Date: Fri, 29 Jan 2016 00:06:00 -0000 [thread overview]
Message-ID: <CACLXh_3eZs=FQVJY7WA8hhkx9TfveLKKStEUE_Yq4mPfSa2aOQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1601282348360.6102@digraph.polyomino.org.uk>
Alright, fair enough. So the solution you want to see is to move
stdint.h out of sysdeps, move the definition of uint_least16_t and
uint_least32_t to a definition of __*_t in bits/stdint.h, and then
define uint_least16_t, uint_least32_t, char16_t, and char32_t on the
basis of the __*_t types? Or is this overkill given that we are
assuming that stdint.h doesn't need to be system-specific? Which would
you prefer?
On Thu, Jan 28, 2016 at 5:51 PM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Thu, 28 Jan 2016, Dwight Guth wrote:
>
>> Would you see it as better to move stdint.h out of sysdeps, or to do
>> something similar to what's done with mbstate_t, NULL, size_t, etc by
>> defining a __need_uint_least16_t and __need_uint_least32_t and having
>> stdint.h define only a __uint_least16_t and __uint_least32_t type and
>> then exit, allowing those types to be used across an abstraction
>> boundary by uchar.h?
>
> I don't think we want to add more __need_* cases; if we split things out,
> it should be by adding a bits/stdint.h header that defines __*_t (and
> moving stdint.h out of sysdeps would still make sense). Cf
> <https://sourceware.org/ml/libc-alpha/2012-08/msg00510.html>.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
next prev parent reply other threads:[~2016-01-29 0:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 20:20 Dwight Guth
2016-01-28 21:19 ` Joseph Myers
2016-01-28 22:20 ` Dwight Guth
2016-01-28 22:48 ` Joseph Myers
2016-01-28 22:50 ` Dwight Guth
2016-01-28 22:52 ` Joseph Myers
2016-01-28 22:58 ` Mike Frysinger
2016-01-28 23:08 ` Dwight Guth
2016-01-28 23:20 ` Joseph Myers
2016-01-28 23:28 ` Dwight Guth
2016-01-28 23:33 ` Joseph Myers
2016-01-28 23:47 ` Dwight Guth
2016-01-28 23:52 ` Joseph Myers
2016-01-29 0:06 ` Dwight Guth [this message]
2016-01-29 15:34 ` Joseph Myers
2016-01-28 23:16 ` Joseph Myers
2016-01-28 23:44 ` Mike Frysinger
2016-01-29 0:48 ` Alexander Cherepanov
2016-01-29 0:58 ` Mike Frysinger
2016-01-30 1:50 ` Alexander Cherepanov
2016-01-31 16:13 ` Joseph Myers
2016-02-03 12:29 ` Undefined behavior in glibc -- was: " Alexander Cherepanov
2016-02-03 13:07 ` Joseph Myers
2016-02-05 18:24 ` Undefined behavior in glibc Alexander Cherepanov
2016-02-05 18:39 ` Joseph Myers
2016-02-05 20:03 ` Alexander Cherepanov
2016-02-05 22:35 ` Joseph Myers
2016-02-10 3:44 ` Alexander Cherepanov
2016-02-10 11:42 ` Szabolcs Nagy
2016-02-10 12:59 ` Joseph Myers
2016-02-01 9:44 ` [PATCH v2][BZ #17979][BZ #17721] Fix issues with sys/cdefs.h and uchar.h when using non-gcc compiler Dwight Guth
2016-02-10 4:16 ` Dwight Guth
2016-02-10 12:59 ` Joseph Myers
2016-02-10 17:21 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACLXh_3eZs=FQVJY7WA8hhkx9TfveLKKStEUE_Yq4mPfSa2aOQ@mail.gmail.com' \
--to=dwight.guth@runtimeverification.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).