public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94291] [10 Regression] ICE: in reg_or_subregno, at jump.c:1928 at -Og since r10-3993-ga79048f6250febc1acce09d790035276d534e754 Date: Tue, 24 Mar 2020 11:47:17 +0000 [thread overview] Message-ID: <bug-94291-4-OCGnOLVYlA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94291-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94291 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |segher at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I guess this is related to PR84169 r8-6756-gba95aa209678e681dcc86df9ebd0a39501c70187 The code assumes that for split_i2i3 SET_DEST must be a REG or SUBREG of REG, but nothing actually checks this. In the testcase it is a MEM instead.
next prev parent reply other threads:[~2020-03-24 11:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-23 18:55 [Bug rtl-optimization/94291] New: [10 Regression] ICE: in reg_or_subregno, at jump.c:1928 at -Og zsojka at seznam dot cz 2020-03-24 6:20 ` [Bug rtl-optimization/94291] " marxin at gcc dot gnu.org 2020-03-24 6:36 ` [Bug rtl-optimization/94291] [10 Regression] ICE: in reg_or_subregno, at jump.c:1928 at -Og since r10-3993-ga79048f6250febc1acce09d790035276d534e754 marxin at gcc dot gnu.org 2020-03-24 11:47 ` jakub at gcc dot gnu.org [this message] 2020-03-24 11:53 ` [Bug target/94291] " jakub at gcc dot gnu.org 2020-04-01 7:48 ` [Bug rtl-optimization/94291] " rguenth at gcc dot gnu.org 2020-04-01 7:57 ` jakub at gcc dot gnu.org 2020-04-07 19:31 ` cvs-commit at gcc dot gnu.org 2020-04-07 20:02 ` jakub at gcc dot gnu.org 2020-04-07 20:39 ` segher at gcc dot gnu.org 2020-04-07 20:42 ` jakub at gcc dot gnu.org 2020-04-07 20:54 ` segher 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-94291-4-OCGnOLVYlA@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).