public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112830] New: internal compiler error: in convert_memory_address_addr_space_1, at explow.cc:302 Date: Sun, 03 Dec 2023 12:22:36 +0000 [thread overview] Message-ID: <bug-112830-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112830 Bug ID: 112830 Summary: internal compiler error: in convert_memory_address_addr_space_1, at explow.cc:302 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: gjl at gcc dot gnu.org Target Milestone: --- Compile the following C test case with avr-gcc -S: typedef __SIZE_TYPE__ size_t; void copy_n (void *vdst, const __memx void *vsrc, size_t n) { typedef struct { char a[n]; } T; T *dst = (T*) vdst; const __memx T *src = (const __memx T*) vsrc; *dst = *src; } during RTL pass: expand ice.c: In function 'copy_n': ce.c:20:10: internal compiler error: in convert_memory_address_addr_space_1, at explow.cc:302 20 | *dst = *src; | ~~~~~^~~~~~ It occurs with at least v5.4 to current master (future v14). Configured with: ../../source/gcc-master/configure --target=avr --disable-nls --with-dwarf2 --with-gnu-as --with-gnu-ld --disable-shared --enable-checking=release --enable-languages=c,c++
next reply other threads:[~2023-12-03 12:22 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-03 12:22 gjl at gcc dot gnu.org [this message] 2023-12-03 12:37 ` [Bug middle-end/112830] " gjl at gcc dot gnu.org 2023-12-03 22:17 ` pinskia at gcc dot gnu.org 2023-12-04 7:06 ` rguenth at gcc dot gnu.org 2023-12-04 8:40 ` rguenth at gcc dot gnu.org 2023-12-04 9:07 ` rguenth at gcc dot gnu.org 2023-12-04 9:08 ` rguenth at gcc dot gnu.org 2023-12-04 9:27 ` rguenth at gcc dot gnu.org 2023-12-04 11:56 ` rguenth at gcc dot gnu.org 2023-12-04 19:19 ` gjl at gcc dot gnu.org 2023-12-05 9:48 ` rguenth at gcc dot gnu.org 2023-12-05 10:54 ` rguenth at gcc dot gnu.org 2023-12-05 11:31 ` ebotcazou at gcc dot gnu.org 2023-12-05 13:55 ` cvs-commit at gcc dot gnu.org 2023-12-05 13:56 ` rguenth at gcc dot gnu.org 2023-12-05 20:46 ` gjl at gcc dot gnu.org 2023-12-06 7:33 ` 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-112830-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).