public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/94526] [10 Regression] cselib ICE building glibc sigpause for m68k and microblaze since r10-7575-g8662d0593438ecd498 Date: Wed, 08 Apr 2020 05:33:48 +0000 [thread overview] Message-ID: <bug-94526-4-6sbtXfoilV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94526-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94526 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10 Regression] cselib ICE |[10 Regression] cselib ICE |building glibc sigpause for |building glibc sigpause for |m68k and microblaze |m68k and microblaze since | |r10-7575-g8662d0593438ecd49 | |8 Known to fail| |10.0 Ever confirmed|0 |1 Known to work| |9.3.0 Target Milestone|--- |10.0 Last reconfirmed| |2020-04-08 Status|UNCONFIRMED |NEW CC| |marxin at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Reduced test-case: $ cat ice.i typedef struct { int __val[8 * sizeof 0]; } __sigset_t; void fn1 (__sigset_t *p1) { __sigset_t *a = p1; } void fn3 (); void fn2 () { __sigset_t b; fn1 (&b); fn3 (b); } $ ./xgcc -B. -O2 -g ice.i during RTL pass: vartrack ice.i: In function ‘fn2’: ice.i:20:1: internal compiler error: in new_elt_loc_list, at cselib.c:298 20 | } | ^ 0xb1538a new_elt_loc_list ../../gcc/cselib.c:298 0xb154ea new_elt_loc_list ../../gcc/cselib.c:322 0xb1a993 cselib_lookup_1 ../../gcc/cselib.c:2301 0xb1aa39 cselib_lookup(rtx_def*, machine_mode, int, machine_mode) ../../gcc/cselib.c:2330 0x15511c7 use_type ../../gcc/var-tracking.c:5516 0x1551741 add_uses ../../gcc/var-tracking.c:5678 0x1551f8e add_uses_1 ../../gcc/var-tracking.c:5832 0x109b117 note_uses(rtx_def**, void (*)(rtx_def**, void*), void*) ../../gcc/rtlanal.c:2042 0x15551c4 add_with_sets ../../gcc/var-tracking.c:6589 0xb1bc1e cselib_record_sets ../../gcc/cselib.c:2835 0xb1c40a cselib_process_insn(rtx_insn*) ../../gcc/cselib.c:2997 0x1560a96 vt_initialize ../../gcc/var-tracking.c:10228 0x156148c variable_tracking_main_1 ../../gcc/var-tracking.c:10457 0x15615d7 variable_tracking_main() ../../gcc/var-tracking.c:10510 0x1561664 execute ../../gcc/var-tracking.c:10547 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2020-04-08 5:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-07 22:33 [Bug middle-end/94526] New: [10 Regression] cselib ICE building glibc sigpause for m68k and microblaze jsm28 at gcc dot gnu.org 2020-04-08 5:33 ` marxin at gcc dot gnu.org [this message] 2020-04-08 6:32 ` [Bug middle-end/94526] [10 Regression] cselib ICE building glibc sigpause for m68k and microblaze since r10-7575-g8662d0593438ecd498 rguenth at gcc dot gnu.org 2020-04-08 11:08 ` jakub at gcc dot gnu.org 2020-04-08 11:17 ` jakub at gcc dot gnu.org 2020-04-08 14:51 ` schwab@linux-m68k.org 2020-04-08 14:53 ` jakub at gcc dot gnu.org 2020-04-08 15:08 ` schwab@linux-m68k.org 2020-04-08 19:24 ` cvs-commit at gcc dot gnu.org 2020-04-08 19:25 ` 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-94526-4-6sbtXfoilV@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).