public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c/448 Date: Tue, 03 Apr 2001 13:36:00 -0000 [thread overview] Message-ID: <20010403203600.13459.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/448; it has been noted by GNATS. From: jsm28@gcc.gnu.org To: gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org Cc: Subject: Re: c/448 Date: 3 Apr 2001 20:30:58 -0000 Synopsis: <stdint.h>-related issues State-Changed-From-To: open->analyzed State-Changed-By: jsm28 State-Changed-When: Tue Apr 3 16:30:58 2001 State-Changed-Why: Confirming my own PR. GCC now has an internal notion of intmax_t and uintmax_t, but no <stdint.h> header. The most recently suggested mechanism for a less fragile <limits.h>, which would also apply to this, would be to have an "enquire"-like program that generates sample <limits.h> and <stdint.h> headers for a given target, then include them in the distribution as with <float.h>. Where the sizes of types can vary on a target, either the target-specific header would need to contain appropriate (potentially fragile) conditionals, or appropriate variant headers would need to be installed in multilib directories. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=448&database=gcc
reply other threads:[~2001-04-03 13:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010403203600.13459.qmail@sourceware.cygnus.com \ --to=jsm28@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).