From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] Introduce hardbool attribute for C
Date: Tue, 09 Aug 2022 10:53:08 -0300 [thread overview]
Message-ID: <or8rnxttff.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orlet4lmn8.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Thu, 07 Jul 2022 16:59:23 -0300")
Ping? (sorry, Joseph, I failed to Cc: you last time)
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598034.html
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598084.html
On Jul 7, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
> for gcc/c-family/ChangeLog
> * c-attribs.cc (c_common_attribute_table): Add hardbool.
> (handle_hardbool_attribute): New.
> (type_valid_for_vector_size): Reject hardbool.
> * c-common.cc (convert_and_check): Skip warnings for convert
> and check for hardbool.
> (c_hardbool_type_attr_1): New.
> * c-common.h (c_hardbool_type_attr): New.
> for gcc/c/ChangeLog
> * c-typeck.cc (convert_lvalue_to_rvalue): Decay hardbools.
> * c-convert.cc (convert): Convert to hardbool through
> truthvalue.
> * c-decl.cc (check_bitfield_type_and_width): Skip enumeral
> truncation warnings for hardbool.
> (finish_struct): Propagate hardbool attribute to bitfield
> types.
> (digest_init): Convert to hardbool.
> for gcc/ChangeLog
> * doc/extend.texi (hardbool): New type attribute.
> for gcc/testsuite/ChangeLog
> * gcc.dg/hardbool-err.c: New.
> * gcc.dg/hardbool-trap.c: New.
> * gcc.dg/hardbool.c: New.
> * gcc.dg/hardbool-s.c: New.
> * gcc.dg/hardbool-us.c: New.
> * gcc.dg/hardbool-i.c: New.
> * gcc.dg/hardbool-ul.c: New.
> * gcc.dg/hardbool-ll.c: New.
> * gcc.dg/hardbool-5a.c: New.
> * gcc.dg/hardbool-s-5a.c: New.
> * gcc.dg/hardbool-us-5a.c: New.
> * gcc.dg/hardbool-i-5a.c: New.
> * gcc.dg/hardbool-ul-5a.c: New.
> * gcc.dg/hardbool-ll-5a.c: New.
--
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:[~2022-08-09 13:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 19:59 Alexandre Oliva
2022-07-08 6:58 ` Richard Biener
2022-07-08 13:39 ` Sebastian Huber
2022-07-08 15:28 ` Alexandre Oliva
2022-07-08 15:28 ` Alexandre Oliva
2022-07-11 9:59 ` Richard Biener
2022-08-09 13:53 ` Alexandre Oliva [this message]
2023-06-16 5:35 ` Alexandre Oliva
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
2023-06-21 15:57 ` Qing Zhao
2023-06-22 2:35 ` Alexandre Oliva
2023-06-23 21:40 ` Qing Zhao
2023-06-24 2:38 ` Alexandre Oliva
2023-06-26 19:05 ` Qing Zhao
2023-06-28 7:26 ` Alexandre Oliva
2023-06-28 15:07 ` Qing Zhao
2023-06-29 10:30 ` Alexandre Oliva
2023-06-29 15:21 ` Qing Zhao
2023-06-24 4:42 ` Alexandre Oliva
2023-10-20 5:31 ` [PATCH v4] " Alexandre Oliva
2023-11-20 12:45 ` Alexandre Oliva
2023-11-20 13:56 ` Richard Biener
2023-11-29 9:30 ` Alexandre Oliva
[not found] ` <20230403012803.29ccf00b@nbbrfq>
[not found] ` <orzg7l8rr4.fsf@lxoliva.fsfla.org>
[not found] ` <6890D6BA-73DC-4F91-9413-228492A7F09B@gmail.com>
[not found] ` <ora5x0x8x9.fsf@lxoliva.fsfla.org>
2023-06-16 6:52 ` [PATCH] " Thomas Koenig
2023-06-16 8:03 ` 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=or8rnxttff.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).