From: Alexandre Oliva <oliva@adacore.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH] Introduce hardbool attribute for C
Date: Fri, 16 Jun 2023 02:39:30 -0300 [thread overview]
Message-ID: <ora5x0x8x9.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <6890D6BA-73DC-4F91-9413-228492A7F09B@gmail.com> (Bernhard Reutner-Fischer's message of "Thu, 06 Apr 2023 13:10:22 +0200")
On Apr 6, 2023, Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> wrote:
> 29 For C_BOOL, the internal representation of .TRUE._C_BOOL and
> .FALSE._C_BOOL shall be the same as those of
> 30 the C values (_Bool)1 and (_Bool)0 respectively.
I'm not changing any of the standard types, FWIW. The proposed
extension enables alternate boolean types to be introduced, with
extra checking for hardening.
> I personally like your proposed 0 and ~0, that's probably pretty robust.
That is only a default. Certain applications may benefit from other
values. 0xa5 and 0x5a seem to make a good combination too.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2023-06-16 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <orlet4lmn8.fsf@lxoliva.fsfla.org>
[not found] ` <or8rnxttff.fsf@lxoliva.fsfla.org>
[not found] ` <20230403012803.29ccf00b@nbbrfq>
[not found] ` <orzg7l8rr4.fsf@lxoliva.fsfla.org>
2023-04-06 11:10 ` Bernhard Reutner-Fischer
2023-06-16 5:39 ` Alexandre Oliva [this message]
2023-06-16 6:52 ` Thomas Koenig
2023-06-16 8:03 ` Alexandre Oliva
[not found] ` <oredmcx940.fsf@lxoliva.fsfla.org>
2023-06-19 18:48 ` Bernhard Reutner-Fischer
2023-06-22 1:08 ` Alexandre Oliva
2023-06-22 21:15 ` Bernhard Reutner-Fischer
2023-06-24 2:57 ` Alexandre Oliva
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=ora5x0x8x9.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=fortran@gcc.gnu.org \
--cc=rep.dot.nop@gmail.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).