public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Tobias Burnus <burnus@net-b.de>
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: <90baa01f0909040617i6e771c3ei33e629f60df80275@mail.gmail.com> (raw)
In-Reply-To: <4AA110EC.3080809@net-b.de>

2009/9/4 Tobias Burnus <burnus@net-b.de>:
> Paolo Bonzini wrote:
>> You can use GCC_STDINT_TYPES (new in this version) instead of
>> GCC_HEADER_STDINT since GCC does not need int_leastNN_t and int_fastNN_t.
>
> That is not completely true. The Fortran front end needs to know the
> storage size of the int_{least,fast}*_t in order to make the
> c_int_{least,fast}*_t kind parameters available in the ISO_C_BINDING
> module (for interoperability with C). The size needs to match the one on
> the target system in order that C and Fortran can interoperate.
>
> I have not checked whether the change affects this (cf.
> gcc/fortran/iso-c-binding.def and users of this file), but one should
> check this before submittal.
>
> Tobias
>

The fortan frontend file iso-c-binding.def depends on target type
nodes of gcc. These are covered by target's stdint definitions, and
not by the build system's stdint header. So there is no mixture
possible AFAIKS (as bootstrap had already shown, too).

Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

  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 13:07 Tobias Burnus
2009-09-04 13:18 ` Kai Tietz [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-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=90baa01f0909040617i6e771c3ei33e629f60df80275@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=bonzini@gnu.org \
    --cc=burnus@net-b.de \
    --cc=gcc-patches@gcc.gnu.org \
    --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).