From: Richard Guenther <richard.guenther@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Henderson <rth@redhat.com>
Subject: Re: [patch]: Add check for stdint header
Date: Thu, 03 Sep 2009 10:55:00 -0000 [thread overview]
Message-ID: <84fc9c000909030355r6843e245j5f5290b021d4ec0e@mail.gmail.com> (raw)
In-Reply-To: <90baa01f0909021518w469a8991ga54bacf8f7df68f9@mail.gmail.com>
On Thu, Sep 3, 2009 at 12:18 AM, Kai Tietz<ktietz70@googlemail.com> wrote:
> Hello,
>
> this patch adds to gcc's system.h file the include of stdint.h file,
> if present. If it doesn't finds this header it defines uintptr_t as
> 'unsigned long' and intptr_t as 'long'.
The toplevel already has support for creating a stdint comaptible header,
you should probably simply use that. See config/stdint*.m4.
Richard.
> ChangeLog
>
> 2009-09-03 Kai Tietz <kai.tietz@onevision.com>
>
> * config.in (HAVE_STDINT_H): New.
> * configure.ac (AC_CHECK_HEADERS): Add stdint.h.
> * configure: Regenerated.
> * system.h: Include stdint.h, if present. Or define default
> versions of uintptr_t and intptr_t with long type.
>
> Tested for x86_64-pc-linux, i686-w64-mingw32, and for
> x86_64-w64-mingw32. Ok for apply to trunk?
>
> Cheers,
> Kai
>
> --
> | (\_/) This is Bunny. Copy and paste
> | (='.'=) Bunny into your signature to help
> | (")_(") him gain world domination
>
next prev parent reply other threads:[~2009-09-03 10:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 22:18 Kai Tietz
2009-09-03 1:37 ` Kai Tietz
2009-09-03 10:55 ` Richard Guenther [this message]
2009-09-03 11:05 ` Kai Tietz
2009-09-03 11:10 ` Richard Guenther
2009-09-04 7:49 ` Kai Tietz
2009-09-04 9:57 ` Richard Guenther
2009-09-04 10:36 ` Paolo Bonzini
[not found] ` <4AA0EE5E.80204@gnu.org>
[not found] ` <90baa01f0909040359r45b5b0c1gfb9132cf800bde9b@mail.gmail.com>
[not found] ` <90baa01f0909040534g4ac57551se2e843b861c42a06@mail.gmail.com>
2009-09-04 13:22 ` Paolo Bonzini
2009-09-06 9:57 ` Ralf Wildenhues
2009-09-04 12:48 Tobias Burnus
2009-09-04 12:53 ` Kai Tietz
2009-09-04 13:18 ` Tobias Burnus
2009-09-04 13:27 ` Paolo Bonzini
2009-09-04 14:07 ` Kai Tietz
2009-09-05 12:41 ` Paolo Bonzini
2009-09-08 15:22 ` Kai Tietz
2009-09-06 10:00 ` Ralf Wildenhues
2009-09-07 6:51 ` Paolo Bonzini
2009-09-04 13:07 Tobias Burnus
2009-09-04 13:18 ` Kai Tietz
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=84fc9c000909030355r6843e245j5f5290b021d4ec0e@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=rth@redhat.com \
/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).