From: "Joseph S. Myers" <joseph@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: proposal to make SIZE_TYPE more flexible
Date: Wed, 30 Oct 2013 22:51:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1310302249250.29408@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201310302219.r9UMJg9e001309@greed.delorie.com>
On Wed, 30 Oct 2013, DJ Delorie wrote:
> So, given all that, is there any way to add the "target-specific
> size_t" portion without waiting for-who-knows-how-long for the intN_t
> and enum-size-type projects to finish? Some form of interim API that
> we can put in, so that we can start working on finding all the
> assumptions about size_t, while waiting for the rest to finish?
I have no idea how ugly something supporting target-specific strings would
be, since supporting such strings for these standard typedefs never seemed
to be a direction we wanted to go in.
(Obviously it's possible to convert only a subset of macros to use enums
rather than strings, or to be hooks rather than macros.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-10-30 22:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 4:28 DJ Delorie
2013-10-30 15:53 ` Joseph S. Myers
2013-10-30 19:18 ` DJ Delorie
2013-10-30 20:49 ` Joseph S. Myers
2013-10-30 22:19 ` DJ Delorie
2013-10-30 22:51 ` Joseph S. Myers [this message]
2013-11-14 1:58 ` DJ Delorie
2013-11-14 13:26 ` Joseph S. Myers
2013-11-14 18:12 ` DJ Delorie
2013-11-14 18:37 ` Joseph S. Myers
2013-11-14 18:48 ` DJ Delorie
2013-11-14 21:40 ` Joseph S. Myers
2013-11-15 1:47 ` DJ Delorie
2013-11-15 1:56 ` Joseph S. Myers
2013-11-15 23:38 ` DJ Delorie
2013-11-16 11:23 ` Richard Biener
2013-11-16 12:26 ` Joseph S. Myers
2013-11-21 22:41 ` DJ Delorie
2013-11-21 22:59 ` Joseph S. Myers
2013-11-22 8:29 ` DJ Delorie
2013-11-22 12:43 ` Joseph S. Myers
2013-11-22 19:33 ` DJ Delorie
2013-11-22 21:00 ` Joseph S. Myers
2013-11-22 21:19 ` DJ Delorie
2013-11-23 0:41 ` Joseph S. Myers
2013-12-10 3:35 ` DJ Delorie
2013-12-10 17:17 ` Joseph S. Myers
2013-12-10 18:10 ` DJ Delorie
2013-12-10 18:38 ` Joseph S. Myers
2013-12-10 18:42 ` DJ Delorie
2013-12-11 9:27 ` Richard Biener
2013-12-20 4:58 ` DJ Delorie
2013-12-20 12:42 ` Joseph S. Myers
2013-12-20 19:47 ` DJ Delorie
2013-12-20 21:53 ` Joseph S. Myers
2013-12-20 21:59 ` DJ Delorie
2013-12-20 22:15 ` Joseph S. Myers
2013-12-20 22:40 ` DJ Delorie
2013-12-21 1:01 ` Joseph S. Myers
2014-01-09 2:31 ` DJ Delorie
2014-01-09 3:23 ` Joseph S. Myers
2014-01-09 7:02 ` DJ Delorie
2014-01-09 16:22 ` Joseph S. Myers
2014-01-15 12:48 ` DJ Delorie
2014-01-28 21:52 ` DJ Delorie
2014-01-28 21:58 ` Joseph S. Myers
2014-01-28 22:24 ` DJ Delorie
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=Pine.LNX.4.64.1310302249250.29408@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.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).