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/106830] [13 Regression] ICE: in tree_to_uhwi, at tree.cc:6392 (from check_for_xor_used_as_pow) since r13-2386-gbedfca647a9e9c1a
Date: Thu, 22 Sep 2022 12:36:37 +0000	[thread overview]
Message-ID: <bug-106830-4-yTLY7jfP20@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106830-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:

https://gcc.gnu.org/g:86254629b636db579616befde49022f098af8148

commit r13-2773-g86254629b636db579616befde49022f098af8148
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Thu Sep 22 08:35:26 2022 -0400

    c: fix uninitialized c_expr::m_decimal [PR106830]

    I added c_expr::m_decimal in r13-2386-gbedfca647a9e9c1a as part of the
    implementation of -Wxor-used-as-pow, but I missed various places where
    the field needed to be initialized.

    Fixed thusly.

    gcc/c-family/ChangeLog:
            PR c/106830
            * c-warn.cc (check_for_xor_used_as_pow): Don't try checking
            values that don't fit in uhwi.

    gcc/c/ChangeLog:
            PR c/106830
            * c-parser.cc (c_parser_initelt): Initialize m_decimal.
            (c_parser_cast_expression): Likewise.
            (c_parser_alignof_expression): Likewise.
            (c_parser_postfix_expression_after_paren_type): Likewise.
            (c_parser_postfix_expression_after_primary): Likewise.
            (c_parser_expression): Likewise.
            (c_parser_omp_variable_list): Likewise.
            (c_parser_transaction_expression): Likewise.
            * c-tree.h (c_expr::set_error): Likewise.
            * c-typeck.cc (c_expr_sizeof_expr): Likewise.
            (parser_build_unary_op): Likewise.
            (parser_build_binary_op): Likewise.
            (digest_init): Likewise.
            (pop_init_level): Likewise.
            * gimple-parser.cc (c_parser_gimple_call_internal): Likewise.

    gcc/testsuite/ChangeLog:
            PR c/106830
            * gcc.dg/Wxor-used-as-pow-pr106830.c: New test.

    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

  parent reply	other threads:[~2022-09-22 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  5:28 [Bug c/106830] New: [13 Regression] ICE: in tree_to_uhwi, at tree.cc:6392 (from check_for_xor_used_as_pow) zsojka at seznam dot cz
2022-09-05  9:11 ` [Bug c/106830] " jakub at gcc dot gnu.org
2022-09-05  9:11 ` jakub at gcc dot gnu.org
2022-09-05 10:12 ` [Bug c/106830] [13 Regression] ICE: in tree_to_uhwi, at tree.cc:6392 (from check_for_xor_used_as_pow) since r13-2386-gbedfca647a9e9c1a marxin at gcc dot gnu.org
2022-09-06  5:06 ` zsojka at seznam dot cz
2022-09-06 15:58 ` dmalcolm at gcc dot gnu.org
2022-09-07  1:24 ` dmalcolm at gcc dot gnu.org
2022-09-22 12:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-22 12:41 ` dmalcolm 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-106830-4-yTLY7jfP20@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).