public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104446] New: [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 Date: Tue, 08 Feb 2022 19:40:31 +0000 [thread overview] Message-ID: <bug-104446-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104446 Bug ID: 104446 Summary: [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- With file ./gcc.target/i386/pr65588.c : $ gcc-12-20220206 -c pr65588.c -O2 -m32 -mrtd -finstrument-functions during RTL pass: combine pr65588.c: In function 't': pr65588.c:10:19: internal compiler error: in trunc_int_for_mode, at explow.cc:59 10 | int t () { a = 0; } | ^ 0x8b5d13 trunc_int_for_mode(long, machine_mode) ../../gcc/explow.cc:59 0x8b5d28 trunc_int_for_mode(poly_int<1u, long>, machine_mode) ../../gcc/explow.cc:86 0x8aa928 gen_int_mode(poly_int<1u, long>, machine_mode) ../../gcc/emit-rtl.cc:542 0xbc3d78 for_each_inc_dec_find_inc_dec ../../gcc/rtlanal.cc:3711 0xbc3d78 for_each_inc_dec(rtx_def*, int (*)(rtx_def*, rtx_def*, rtx_def*, rtx_def*, rtx_def*, void*), void*) ../../gcc/rtlanal.cc:3750 0x17597af try_combine ../../gcc/combine.cc:3346 0x175f3cc combine_instructions ../../gcc/combine.cc:1269 0x175f3cc rest_of_handle_combine ../../gcc/combine.cc:14922 0x175f3cc execute ../../gcc/combine.cc:14967
next reply other threads:[~2022-02-08 19:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-08 19:40 gscfq@t-online.de [this message] 2022-02-08 21:37 ` [Bug middle-end/104446] " pinskia at gcc dot gnu.org 2022-02-09 7:32 ` rguenth at gcc dot gnu.org 2022-02-09 9:04 ` [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 since r9-6999 jakub at gcc dot gnu.org 2022-02-09 11:13 ` jakub at gcc dot gnu.org 2022-02-09 11:32 ` jakub at gcc dot gnu.org 2022-02-10 7:47 ` segher at gcc dot gnu.org 2022-02-11 12:52 ` cvs-commit at gcc dot gnu.org 2022-02-11 12:53 ` [Bug middle-end/104446] [9/10/11 " jakub at gcc dot gnu.org 2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:08 ` [Bug middle-end/104446] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:23 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-104446-4@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: linkBe 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).