public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: gfc_char_t
Date: Sun, 9 Jan 2022 23:22:37 +0100	[thread overview]
Message-ID: <293768dc-f61e-b4e2-e499-70ac3fdf0165@gmx.de> (raw)
Message-ID: <20220109222237.DrQa9PDtwdsTZneDLXIcWeh5IeBVofAUOEO5W9A_1Ww@z> (raw)
In-Reply-To: <CA+=Sn1=37qyWyXyDkXC2M83AeJedTQGExsJDVduRhxD3m=+ang@mail.gmail.com>

Hi Andrew,

Am 09.01.22 um 23:00 schrieb Andrew Pinski via Fortran:
> On Sun, Jan 9, 2022 at 1:46 PM Harald Anlauf via Fortran
> I suspect HOST_BITS_PER_INT will always be 32bit for all hosts GCC
> will be supported but who knows. The point of the check is to find a
> type which is at least 32bits enough to hold the wide character.
> HOST_BITS_PER_* are defined in hwint.h:
> #define HOST_BITS_PER_CHAR  CHAR_BIT
> #define HOST_BITS_PER_SHORT (CHAR_BIT * SIZEOF_SHORT)
> #define HOST_BITS_PER_INT   (CHAR_BIT * SIZEOF_INT)
> #define HOST_BITS_PER_LONG  (CHAR_BIT * SIZEOF_LONG)
> #define HOST_BITS_PER_PTR   (CHAR_BIT * SIZEOF_VOID_P)
> 
> Where SIZEOF_* are defined while doing a configure and CHAR_BIT is
> defined in limits.h which is defined as a preprocessor constant.
> Does that help you understand the code better?

ok, that makes things clearer now.

(I've actually never looked into hwint.h before.  I should have.)

Thanks,
Harald

> Thanks,
> Andrew Pinski
> 
> 
>>
>> Thanks for any enlightenment,
>> Harald
>>
> 



  reply	other threads:[~2022-01-09 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 21:46 gfc_char_t Harald Anlauf
2022-01-09 22:00 ` gfc_char_t Andrew Pinski
2022-01-09 22:22   ` Harald Anlauf [this message]
2022-01-09 22:22     ` gfc_char_t Harald Anlauf

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=293768dc-f61e-b4e2-e499-70ac3fdf0165@gmx.de \
    --to=anlauf@gmx.de \
    --cc=fortran@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: 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).