public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cnsun at uwaterloo dot ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/101017] New: ICE: Segmentation fault, convert_memory_address_addr_space_1(scalar_int_mode, rtx_def*, unsigned char, bool, bool) Date: Thu, 10 Jun 2021 14:23:37 +0000 [thread overview] Message-ID: <bug-101017-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101017 Bug ID: 101017 Summary: ICE: Segmentation fault, convert_memory_address_addr_space_1(scalar_int_mode, rtx_def*, unsigned char, bool, bool) Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: cnsun at uwaterloo dot ca Target Milestone: --- $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/scratch/software/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /tmp/tmp.MAuXx9TiBr-gcc-builder/gcc/configure --enable-languages=c,c++,lto --enable-checking-yes --enable-multiarch --prefix=/scratch/software/gcc-trunk --disable-bootstrap Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20210610 (experimental) [master revision :71aa05def:4f625f47b4456e5c05a025fca4d072831e59126c] (GCC) $ cat mutant.c typedef v32qi __attribute__((vector_size(32))); __attribute__((target_clones("arch=core-avx2", "default"))) v32qi foo_ashift_256() {} $ gcc-trunk mutant.c mutant.c:1:9: warning: type defaults to ‘int’ in declaration of ‘v32qi’ [-Wimplicit-int] 1 | typedef v32qi __attribute__((vector_size(32))); | ^~~~~ mutant.c: In function ‘foo_ashift_256’: mutant.c:3:1: warning: AVX vector return without AVX enabled changes the ABI [-Wpsabi] 3 | foo_ashift_256() {} | ^~~~~~~~~~~~~~ during RTL pass: expand mutant.c: In function ‘foo_ashift_256.arch_core_avx2.0’: mutant.c:3:19: internal compiler error: Segmentation fault 3 | foo_ashift_256() {} | ^ 0xf0a1a3 crash_signal /tmp/tmp.MAuXx9TiBr-gcc-builder/gcc/gcc/toplev.c:327 0xb53029 convert_memory_address_addr_space_1(scalar_int_mode, rtx_def*, unsigned char, bool, bool) /tmp/tmp.MAuXx9TiBr-gcc-builder/gcc/gcc/explow.c:309 0xbdf25b expand_function_end() /tmp/tmp.MAuXx9TiBr-gcc-builder/gcc/gcc/function.c:5517 0xa50992 construct_exit_block /tmp/tmp.MAuXx9TiBr-gcc-builder/gcc/gcc/cfgexpand.c:6194 0xa50992 execute /tmp/tmp.MAuXx9TiBr-gcc-builder/gcc/gcc/cfgexpand.c:6812 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:[~2021-06-10 14:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 14:23 cnsun at uwaterloo dot ca [this message] 2021-06-11 11:41 ` [Bug target/101017] ICE: Segmentation fault, convert_memory_address_addr_space_1 with vector_size(32) and target_clone arch=core-avx2/default marxin at gcc dot gnu.org 2021-12-20 2:35 ` pinskia at gcc dot gnu.org 2021-12-20 8:50 ` marxin at gcc dot gnu.org 2023-12-03 22:07 ` pinskia at gcc dot gnu.org 2023-12-04 4:03 ` liuhongt at gcc dot gnu.org 2023-12-05 5:38 ` liuhongt at gcc dot gnu.org 2024-05-13 6:09 ` liuhongt 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-101017-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).