public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97528] New: [10/11 Regression] ICE in decompose_automod_address, at rtlanal.c:6298 (arm-linux-gnueabihf) Date: Thu, 22 Oct 2020 11:42:40 +0000 [thread overview] Message-ID: <bug-97528-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97528 Bug ID: 97528 Summary: [10/11 Regression] ICE in decompose_automod_address, at rtlanal.c:6298 (arm-linux-gnueabihf) Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: doko at debian dot org Target Milestone: --- seen on the gcc-10 branch 2020-10-11 and trunk, building firefox. $ cat intrapred_neon.i typedef __simd64_int16_t a; typedef __simd64_uint16_t b; unsigned short c; int d; b e; void f() { unsigned short *dst = &c; int g = d, bw = 4; b dc = e; for (int h = 0; h < bw; h++) { unsigned short *i = dst; b j = dc; __builtin_neon_vst1v4hi((__builtin_neon_hi *)i, (a)j); dst += g; } } $ gcc -o intrapred_neon.o -c -O1 -mfpu=neon intrapred_neon.i during RTL pass: reload /home/glandium/firefox-esr-78.4.0esr/third_party/aom/aom_dsp/arm/intrapred_neon.c: In function 'aom_highbd_dc_predictor_4x4_neon': /home/glandium/firefox-esr-78.4.0esr/third_party/aom/aom_dsp/arm/intrapred_neon.c:589:188: internal compiler error: in decompose_automod_address, at rtlanal.c:6298 0x6cda45 decompose_automod_address ../../src/gcc/rtlanal.c:6298 0x6cda45 decompose_address(address_info*, rtx_def**, machine_mode, unsigned char, rtx_code) ../../src/gcc/rtlanal.c:6463 0x6cdb19 decompose_mem_address(address_info*, rtx_def*) ../../src/gcc/rtlanal.c:6486 0x59a67b process_address_1 ../../src/gcc/lra-constraints.c:3374 0x59c4cd process_address ../../src/gcc/lra-constraints.c:3648 0x59c4cd curr_insn_transform ../../src/gcc/lra-constraints.c:3963 0x5a088f lra_constraints(bool) ../../src/gcc/lra-constraints.c:5036 0x58e7a5 lra(_IO_FILE*) ../../src/gcc/lra.c:2443 0x54f331 do_reload ../../src/gcc/ira.c:5527 0x54f331 execute ../../src/gcc/ira.c:5713 Please submit a full bug report, with preprocessed source if appropriate. gcc-10 was configured with --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --enable-checking=yes,extra,rtl --enable-default-pie gcc trunk was configure with --enable-checking=yes
next reply other threads:[~2020-10-22 11:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-22 11:42 doko at debian dot org [this message] 2020-10-22 11:52 ` [Bug target/97528] " rguenth at gcc dot gnu.org 2020-10-23 11:25 ` ktkachov at gcc dot gnu.org 2020-11-18 16:12 ` [Bug target/97528] [9/10/11 " jakub at gcc dot gnu.org 2020-11-18 16:14 ` jakub at gcc dot gnu.org 2020-11-20 11:27 ` cvs-commit at gcc dot gnu.org 2020-11-20 11:42 ` [Bug target/97528] [9/10 " jakub at gcc dot gnu.org 2020-11-25 11:56 ` cvs-commit at gcc dot gnu.org 2021-02-01 13:28 ` avieira at gcc dot gnu.org 2021-02-01 13:30 ` ktkachov at gcc dot gnu.org 2021-02-01 13:36 ` jakub at gcc dot gnu.org 2021-02-03 10:03 ` cvs-commit at gcc dot gnu.org 2021-02-03 18:32 ` cvs-commit at gcc dot gnu.org 2021-02-03 18:33 ` avieira at gcc dot gnu.org 2021-02-03 18:37 ` 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-97528-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).