From: Tobias Burnus <burnus@net-b.de>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: gcc patches <gcc-patches@gcc.gnu.org>,
Paolo Bonzini <bonzini@gnu.org>,
Richard Guenther <rguenther@suse.de>,
Richard Henderson <rth@redhat.com>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Subject: Re: [patch]: Add check for stdint header
Date: Fri, 04 Sep 2009 13:18:00 -0000 [thread overview]
Message-ID: <4AA11386.2000007@net-b.de> (raw)
In-Reply-To: <90baa01f0909040552v1b27414bo37a7e60ad0438b5b@mail.gmail.com>
On 09/04/2009 02:52 PM, Kai Tietz wrote:
> Well, I bootstrapped this with Paolo's stdint.m4 patch, and it
> workedon linux32 and linux64 (i386), and for x86_64-pc-mingw32, too.
> Just out of curiosity, who is the size in gfortran frontend for
> int_{least,fast}*_t done, as for gcc until now no stdint.h/inttypes.h
> file was used?
>
Actually, I do not know how exactly it works ... I now checked - and
here is how it works:
In gcc/fortran/ one calls:
TYPE_PRECISION (type)
for INT_FAST64_TYPE etc. The defaults are set in
gcc/default.h
For instance:
#ifndef INT_FAST64_TYPE
#define INT_FAST64_TYPE ((const char *) NULL)
#endif
And the INT_*_TYPE definitions can seemingly found in
config/*/*stdint.h. For instance:
./i386/cygwin-stdint.h:#define INT_FAST64_TYPE "long long int"
./i386/mingw-stdint.h:#define INT_FAST64_TYPE "long long int"
./glibc-stdint.h:#define INT_FAST64_TYPE (LONG_TYPE_SIZE == 64 ? "long
int" : "long long int")
Thus, stdint.h is not directly involved and the patch should have no
(adverse) effect on gfortran's c_int_fast*_t support.
Tobias
next prev parent reply other threads:[~2009-09-04 13:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 12:48 Tobias Burnus
2009-09-04 12:53 ` Kai Tietz
2009-09-04 13:18 ` Tobias Burnus [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 13:07 Tobias Burnus
2009-09-04 13:18 ` Kai Tietz
2009-09-02 22:18 Kai Tietz
2009-09-03 1:37 ` Kai Tietz
2009-09-03 10:55 ` Richard Guenther
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
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=4AA11386.2000007@net-b.de \
--to=burnus@net-b.de \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=rguenther@suse.de \
--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).