public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/98629] New: ice during GIMPLE pass: widening_mul Date: Mon, 11 Jan 2021 21:32:04 +0000 [thread overview] Message-ID: <bug-98629-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98629 Bug ID: 98629 Summary: ice during GIMPLE pass: widening_mul Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this reduced C code: unsigned int a; int b, c; void d() { unsigned int *e = &a; (a /= a |= b) - (0 <= (*e += *e)) * (c *= *e); } does this with recent gcc trunk: $ /home/dcb/gcc/results.20210111/bin/gcc -c -w -O2 bug689.c during GIMPLE pass: widening_mul bug689.c: In function ‘d’: bug689.c:3:6: internal compiler error: Segmentation fault 3 | void d() { | ^ 0xcd63f9 crash_signal(int) ../../trunk.git/gcc/toplev.c:327 0xe7b538 gimple_code(gimple const*) ../../trunk.git/gcc/gimple.h:1782 0xe7b538 is_gimple_assign(gimple const*) ../../trunk.git/gcc/gimple.h:2529 0xe7b538 gimple_assign_cast_p(gimple const*) ../../trunk.git/gcc/gimple.h:2870 The bug first seems to appear sometime between date 20210108 and today i.e. 20210111. Hashes for those dates are bdcde15045027195 and 9a6c37e6ae520534. with 32 commits between them. Jakub's recent changes to widening_mul look a likely candidate. I don't see much point in doing a git bisect, although I can if requested. Jakub's
next reply other threads:[~2021-01-11 21:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-11 21:32 dcb314 at hotmail dot com [this message] 2021-01-11 21:49 ` [Bug c/98629] " dcb314 at hotmail dot com 2021-01-11 22:47 ` [Bug tree-optimization/98629] [11 Regression] " jakub at gcc dot gnu.org 2021-01-11 23:03 ` jakub at gcc dot gnu.org 2021-01-12 10:05 ` cvs-commit at gcc dot gnu.org 2021-01-15 0:46 ` 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-98629-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).