public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103938] New: ICE with __builtin_prefetch and vectors Date: Fri, 07 Jan 2022 10:12:44 +0000 [thread overview] Message-ID: <bug-103938-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103938 Bug ID: 103938 Summary: ICE with __builtin_prefetch and vectors Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-checking, ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Take: typedef unsigned long u64x2 __attribute__ ((vector_size(16))); void g (u64x2 off) { __builtin_prefetch ((void*)off[0], 0, 3); } This ICEs at -O2 and above. during RTL pass: sched1 dump file: t.c.296r.sched1 t.c: In function 'g': t.c:5:1: internal compiler error: in aarch64_classify_address, at config/aarch64/aarch64.c:9966 5 | } | ^ 0x1156ee3 aarch64_classify_address(aarch64_address_info*, rtx_def*, machine_mode, bool, aarch64_addr_query_type) /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/config/aarch64/aarch64.c:9966 0x1156f03 aarch64_address_valid_for_prefetch_p(rtx_def*, bool) /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/config/aarch64/aarch64.c:10233 0xb93bbb constraint_satisfied_p ./tm-preds.h:348 0xb93bbb record_reg_classes /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/ira-costs.c:794 0xb954a7 record_operand_costs /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/ira-costs.c:1440 0xb95813 scan_one_insn /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/ira-costs.c:1527 0xb95813 process_bb_for_costs /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/ira-costs.c:1652 0xb96e1f find_costs_and_classes /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/ira-costs.c:1759 0xb9771b ira_set_pseudo_classes(bool, _IO_FILE*) /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/ira-costs.c:2313 0x1964fe7 alloc_global_sched_pressure_data /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/haifa-sched.c:7201 0x1964fe7 sched_init() /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/haifa-sched.c:7356 0x19668db haifa_sched_init() /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/haifa-sched.c:7368 0xd327e7 schedule_insns() /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/sched-rgn.c:3510 0xd32f9f schedule_insns() /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/sched-rgn.c:3504 0xd32f9f rest_of_handle_sched /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/sched-rgn.c:3722 0xd32f9f execute /home/ubuntu/src/upstream-gcc-aarch64/gcc/gcc/sched-rgn.c:3830 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 reply other threads:[~2022-01-07 10:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-07 10:12 pinskia at gcc dot gnu.org [this message] 2022-01-07 10:51 ` [Bug target/103938] " pinskia at gcc dot gnu.org 2022-01-28 0:33 ` [Bug target/103938] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-28 0:35 ` pinskia at gcc dot gnu.org 2022-04-06 16:28 ` acoplan at gcc dot gnu.org 2022-04-06 16:36 ` pinskia at gcc dot gnu.org 2022-04-07 9:17 ` acoplan at gcc dot gnu.org 2022-04-19 15:30 ` rguenth at gcc dot gnu.org 2022-04-28 17:29 ` [Bug target/103938] [9/10/11/12/13 " acoplan at gcc dot gnu.org 2022-04-28 19:14 ` pinskia at gcc dot gnu.org 2022-05-27 9:47 ` [Bug target/103938] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:47 ` jakub at gcc dot gnu.org 2023-07-07 10:41 ` [Bug target/103938] [11/12/13/14 " rguenth 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-103938-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).