public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102989] Implement C2x's n2763 (_BitInt)
Date: Wed, 06 Sep 2023 15:58:01 +0000	[thread overview]
Message-ID: <bug-102989-4-4ICMvOd36y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102989-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989

--- Comment #102 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:8c984a1c3693df63520558631c827bb2c2d8b5bc

commit r14-3751-g8c984a1c3693df63520558631c827bb2c2d8b5bc
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Sep 6 17:34:49 2023 +0200

    C _BitInt support [PR102989]

    This patch adds the C FE support, c-family support, small libcpp change
    so that 123wb and 42uwb suffixes are handled plus glimits.h change
    to define BITINT_MAXWIDTH macro.

    The previous patches really do nothing without this, which enables
    all the support.

    2023-09-06  Jakub Jelinek  <jakub@redhat.com>

            PR c/102989
    gcc/
            * glimits.h (BITINT_MAXWIDTH): Define if __BITINT_MAXWIDTH__ is
            predefined.
    gcc/c-family/
            * c-common.cc (c_common_reswords): Add _BitInt as keyword.
            (unsafe_conversion_p): Handle BITINT_TYPE like INTEGER_TYPE.
            (c_common_signed_or_unsigned_type): Handle BITINT_TYPE.
            (c_common_truthvalue_conversion, c_common_get_alias_set,
            check_builtin_function_arguments): Handle BITINT_TYPE like
            INTEGER_TYPE.
            (sync_resolve_size): Add ORIG_FORMAT argument.  If
            FETCH && !ORIG_FORMAT, type is BITINT_TYPE, return -1 if size isn't
            one of 1, 2, 4, 8 or 16 or if it is 16 but TImode is not supported.
            (atomic_bitint_fetch_using_cas_loop): New function.
            (resolve_overloaded_builtin): Adjust sync_resolve_size caller.  If
            -1 is returned, use atomic_bitint_fetch_using_cas_loop to lower it.
            Formatting fix.
            (keyword_begins_type_specifier): Handle RID_BITINT.
            * c-common.h (enum rid): Add RID_BITINT enumerator.
            * c-cppbuiltin.cc (c_cpp_builtins): For C call
            targetm.c.bitint_type_info and predefine __BITINT_MAXWIDTH__
            and for -fbuilding-libgcc also __LIBGCC_BITINT_LIMB_WIDTH__ and
            __LIBGCC_BITINT_ORDER__ macros if _BitInt is supported.
            * c-lex.cc (interpret_integer): Handle CPP_N_BITINT.
            * c-pretty-print.cc (c_pretty_printer::simple_type_specifier,
            c_pretty_printer::direct_abstract_declarator,
            c_pretty_printer::direct_declarator, c_pretty_printer::declarator):
            Handle BITINT_TYPE.
            (pp_c_integer_constant): Handle printing of large precision
wide_ints
            which would buffer overflow digit_buffer.
            * c-warn.cc (conversion_warning, warnings_for_convert_and_check,
            warnings_for_convert_and_check): Handle BITINT_TYPE like
            INTEGER_TYPE.
    gcc/c/
            * c-convert.cc (c_convert): Handle BITINT_TYPE like INTEGER_TYPE.
            * c-decl.cc (check_bitfield_type_and_width): Allow BITINT_TYPE
            bit-fields.
            (finish_struct): Prefer to use BITINT_TYPE for BITINT_TYPE
bit-fields
            if possible.
            (declspecs_add_type): Formatting fixes.  Handle cts_bitint.  Adjust
            for added union in *specs.  Handle RID_BITINT.
            (finish_declspecs): Handle cts_bitint.  Adjust for added union
            in *specs.
            * c-parser.cc (c_keyword_starts_typename, c_token_starts_declspecs,
            c_parser_declspecs, c_parser_gnu_attribute_any_word): Handle
            RID_BITINT.
            (c_parser_omp_clause_schedule): Handle BITINT_TYPE like
INTEGER_TYPE.
            * c-tree.h (enum c_typespec_keyword): Mention _BitInt in comment.
            Add cts_bitint enumerator.
            (struct c_declspecs): Move int_n_idx and floatn_nx_idx into a union
            and add bitint_prec there as well.
            * c-typeck.cc (c_common_type, comptypes_internal):
            Handle BITINT_TYPE.
            (perform_integral_promotions): Promote BITINT_TYPE bit-fields to
            their declared type.
            (build_array_ref, build_unary_op, build_conditional_expr,
            build_c_cast, convert_for_assignment, digest_init,
build_binary_op):
            Handle BITINT_TYPE.
            * c-fold.cc (c_fully_fold_internal): Handle BITINT_TYPE like
            INTEGER_TYPE.
            * c-aux-info.cc (gen_type): Handle BITINT_TYPE.
    libcpp/
            * expr.cc (interpret_int_suffix): Handle wb and WB suffixes.
            * include/cpplib.h (CPP_N_BITINT): Define.

  parent reply	other threads:[~2023-09-06 15:58 UTC|newest]

Thread overview: 119+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 17:41 [Bug c/102989] New: Add Clang's _ExtInt(N) colomar.6.4.3 at gmail dot com
2021-10-28 17:54 ` [Bug c/102989] " colomar.6.4.3 at gmail dot com
2021-10-28 17:57 ` colomar.6.4.3 at gmail dot com
2021-10-28 17:57 ` colomar.6.4.3 at gmail dot com
2021-10-28 18:01 ` jakub at gcc dot gnu.org
2021-10-28 18:11 ` colomar.6.4.3 at gmail dot com
2021-10-28 21:41 ` joseph at codesourcery dot com
2021-10-28 21:47 ` [Bug c/102989] Implement C2x's n2763 (_BitInt) pinskia at gcc dot gnu.org
2021-10-28 21:49 ` pinskia at gcc dot gnu.org
2021-11-11 19:42 ` pinskia at gcc dot gnu.org
2021-11-11 19:58 ` colomar.6.4.3 at gmail dot com
2021-11-11 21:27 ` joseph at codesourcery dot com
2022-10-25 12:14 ` jakub at gcc dot gnu.org
2022-10-25 15:25 ` hjl.tools at gmail dot com
2022-10-25 20:32 ` joseph at codesourcery dot com
2022-10-25 20:42 ` hjl.tools at gmail dot com
2022-10-25 20:45 ` jakub at gcc dot gnu.org
2022-10-25 21:05 ` segher at gcc dot gnu.org
2022-10-25 21:05 ` hjl.tools at gmail dot com
2022-10-25 21:09 ` pinskia at gcc dot gnu.org
2022-10-25 21:10 ` jakub at gcc dot gnu.org
2022-10-25 21:30 ` segher at gcc dot gnu.org
2022-10-25 21:50 ` segher at gcc dot gnu.org
2022-10-26  6:29 ` uweigand at gcc dot gnu.org
2022-10-26  6:50 ` jakub at gcc dot gnu.org
2022-10-26  8:35 ` redi at gcc dot gnu.org
2022-10-26 17:29 ` joseph at codesourcery dot com
2022-10-28  9:47 ` rguenth at gcc dot gnu.org
2022-10-28 10:32 ` jakub at gcc dot gnu.org
2022-10-28 10:51 ` rguenther at suse dot de
2022-10-28 11:02 ` colomar.6.4.3 at gmail dot com
2022-10-28 17:27 ` pinskia at gcc dot gnu.org
2022-10-28 20:31 ` joseph at codesourcery dot com
2022-10-28 20:39 ` joseph at codesourcery dot com
2023-04-09 19:59 ` leni536 at gmail dot com
2023-04-12 22:17 ` george at bott dot gg
2023-05-11 18:00 ` jakub at gcc dot gnu.org
2023-05-11 18:21 ` jakub at gcc dot gnu.org
2023-05-11 22:10 ` joseph at codesourcery dot com
2023-05-12  7:46 ` jakub at gcc dot gnu.org
2023-05-12  8:41 ` rguenth at gcc dot gnu.org
2023-05-16 16:20 ` jakub at gcc dot gnu.org
2023-05-17  7:22 ` rguenth at gcc dot gnu.org
2023-05-23 12:04 ` jakub at gcc dot gnu.org
2023-05-24 11:48 ` jakub at gcc dot gnu.org
2023-05-24 12:46 ` rguenther at suse dot de
2023-05-24 13:16 ` jakub at gcc dot gnu.org
2023-05-24 13:29 ` rguenther at suse dot de
2023-05-24 14:18 ` jakub at gcc dot gnu.org
2023-05-24 14:57 ` rguenther at suse dot de
2023-05-24 15:31 ` jakub at gcc dot gnu.org
2023-05-26 16:13 ` jakub at gcc dot gnu.org
2023-05-26 16:16 ` jakub at gcc dot gnu.org
2023-05-26 17:11 ` jakub at gcc dot gnu.org
2023-06-02 10:39 ` jakub at gcc dot gnu.org
2023-06-02 10:43 ` rguenther at suse dot de
2023-06-02 10:53 ` jakub at gcc dot gnu.org
2023-06-02 17:06 ` jakub at gcc dot gnu.org
2023-06-05  7:14 ` rguenth at gcc dot gnu.org
2023-06-05  7:34 ` jakub at gcc dot gnu.org
2023-06-05  7:43 ` rguenth at gcc dot gnu.org
2023-06-05  7:58 ` jakub at gcc dot gnu.org
2023-06-05  8:21 ` rguenther at suse dot de
2023-06-05  8:33 ` jakub at gcc dot gnu.org
2023-06-06  7:13 ` rguenth at gcc dot gnu.org
2023-06-15 11:28 ` jakub at gcc dot gnu.org
2023-06-15 18:02 ` jakub at gcc dot gnu.org
2023-06-19 17:40 ` jakub at gcc dot gnu.org
2023-06-20 20:04 ` jakub at gcc dot gnu.org
2023-06-22 19:47 ` jakub at gcc dot gnu.org
2023-06-23 17:03 ` jakub at gcc dot gnu.org
2023-06-26 18:48 ` jakub at gcc dot gnu.org
2023-06-28 17:21 ` jakub at gcc dot gnu.org
2023-06-29 17:01 ` jakub at gcc dot gnu.org
2023-06-30 19:22 ` jakub at gcc dot gnu.org
2023-07-05 17:23 ` jakub at gcc dot gnu.org
2023-07-07 14:26 ` jakub at gcc dot gnu.org
2023-07-07 17:59 ` jakub at gcc dot gnu.org
2023-07-11 11:20 ` jakub at gcc dot gnu.org
2023-07-12 16:28 ` jakub at gcc dot gnu.org
2023-07-13 18:03 ` jakub at gcc dot gnu.org
2023-07-14 11:18 ` jakub at gcc dot gnu.org
2023-07-14 11:18 ` jakub at gcc dot gnu.org
2023-07-14 17:19 ` jakub at gcc dot gnu.org
2023-07-17 10:21 ` jakub at gcc dot gnu.org
2023-07-17 18:06 ` jakub at gcc dot gnu.org
2023-07-18 11:07 ` jakub at gcc dot gnu.org
2023-07-18 15:45 ` jakub at gcc dot gnu.org
2023-07-20 15:51 ` jakub at gcc dot gnu.org
2023-07-21 17:10 ` jakub at gcc dot gnu.org
2023-07-25 14:40 ` jakub at gcc dot gnu.org
2023-07-26 13:04 ` jakub at gcc dot gnu.org
2023-07-26 17:41 ` jakub at gcc dot gnu.org
2023-07-27 15:18 ` jakub at gcc dot gnu.org
2023-08-10  7:22 ` cvs-commit at gcc dot gnu.org
2023-08-10  7:23 ` cvs-commit at gcc dot gnu.org
2023-08-10 15:30 ` cvs-commit at gcc dot gnu.org
2023-08-14 21:55 ` tmgross at umich dot edu
2023-09-06 15:57 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:57 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:57 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:57 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:57 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:57 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-06 15:58 ` cvs-commit at gcc dot gnu.org
2023-09-07  9:21 ` cvs-commit at gcc dot gnu.org
2023-10-12 14:07 ` cvs-commit at gcc dot gnu.org
2023-10-14  7:38 ` cvs-commit at gcc dot gnu.org
2023-10-14 22:38 ` gaius at gcc dot gnu.org
2023-11-01  8:17 ` gaius at gcc dot gnu.org
2023-11-01  9:06 ` cvs-commit at gcc dot gnu.org

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=bug-102989-4-4ICMvOd36y@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).