This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Detemining the size of int_fast8_t etc. in the frontend
- From: François-Xavier Coudert <Francois-Xavier dot Coudert at lcp dot u-psud dot fr>
- To: Tobias Burnus <burnus at net-b dot de>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 7 Mar 2007 22:10:19 +0100
- Subject: Re: Detemining the size of int_fast8_t etc. in the frontend
Hi Tobias,
What is the proper way to obtain this information?
I fear the answer to this question is "there's no way". We already
discussed that a few months ago, at the thread starting here: http://
gcc.gnu.org/ml/gcc/2006-10/msg00346.html From private discussion,
with Paul Brook & Joseph Myers IIRC, the conclusion is that GCC can't
do that right now, but it could if target-specific files provided the
information. Maybe there's a PR open for that, otherwise you can open
it, and we can try to get people implement the framework for this...
Christopher's original ISO_C_BINDING patch used autoconf to guess it,
and I remove that (before creating the fortran-experiments branch).
Currently, there's no other option than to return -2 for the
corresponding ISO_C_BINDING constants.
FXAttachment:
smime.p7s
Description: S/MIME cryptographic signature