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] internal compiler error: in convert_memory_address_addr_space_1, at explow.cc:302 Date: Mon, 04 Dec 2023 19:19:31 +0000 [thread overview] Message-ID: <bug-112830-4-WbswnfCd2E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112830-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112830 --- Comment #9 from Georg-Johann Lay <gjl at gcc dot gnu.org> --- (In reply to Richard Biener from comment #8) > Is there a valid testcase that has __memx as the destination? Or is there > an address space with similar constraints that allows non-const accesses? No. The avr backend throws an error when a non-generic address space thing is not const, like __memx int var; int f1 (__memx int *p) { return *p; } foo.c:1:12: error: variable 'var' must be const in order to be put into read-only section by means of '__memx' 1 | __memx int var; | ^~~ foo.c:3:21: error: pointer targeting address space '__memx' must be const in function parameter 'p' 3 | int f1 (__memx int *p) | ~~~~~~~~~~~~^ __memx covers all address spacec, including generic. But in order to write one has to cast it to a generic pointer (after checking that it actually points to generic and not somewhere else (flash)). (In reply to Richard Biener from comment #3) > I think the assert can be relaxed to make truncation OK. A truncation from 24-bit __memx address to some other AS (all 16 bits) would require a run-time check which 16-bit AS it encodes, and depending on that execute code fit for that AS. This is ok when the user is doing it, but the compiler should never require any kind of truncation. And extension / casts are handled by TARGET_ADDR_SPACE_CONVERT.
next prev parent reply other threads:[~2023-12-04 19:19 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-03 12:22 [Bug middle-end/112830] New: " gjl at gcc dot gnu.org 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 [this message] 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-WbswnfCd2E@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).