public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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 09:07:44 +0000 [thread overview] Message-ID: <bug-112830-4-56J1LDYgqd@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Note we end up trying to expand a memcpy between different address spaces and that does addr = expand_expr (orig_exp, NULL_RTX, ptr_mode, EXPAND_NORMAL); mem = gen_rtx_MEM (BLKmode, memory_address (BLKmode, addr)); which assumes the default address-space. The get_memory_rtx () function also doesn't correctly preserve the address-space for the MEM_EXPR. The following fixes the ICE and tries to correct the MEM_EXPR. But I wonder if the actual code generation is sane? It also appears we'd eventually emit a call to memcpy as we call emit_block_move_hints with BLOCK_OP_NORMAL which sets may_use_call to 1. So, can you check whether we generate correct code with the following patch? Otherwise we should keep it ICEing (wrong-code is IMHO worse). diff --git a/gcc/builtins.cc b/gcc/builtins.cc index 4fc58a0bda9..244863699be 100644 --- a/gcc/builtins.cc +++ b/gcc/builtins.cc @@ -1353,7 +1353,8 @@ get_memory_rtx (tree exp, tree len) exp = TREE_OPERAND (exp, 0); addr = expand_expr (orig_exp, NULL_RTX, ptr_mode, EXPAND_NORMAL); - mem = gen_rtx_MEM (BLKmode, memory_address (BLKmode, addr)); + addr_space_t as = TYPE_ADDR_SPACE (TREE_TYPE (TREE_TYPE (exp))); + mem = gen_rtx_MEM (BLKmode, memory_address_addr_space (BLKmode, addr, as)); /* Get an expression we can use to find the attributes to assign to MEM. First remove any nops. */ @@ -1363,8 +1364,11 @@ get_memory_rtx (tree exp, tree len) /* Build a MEM_REF representing the whole accessed area as a byte blob, (as builtin stringops may alias with anything). */ + tree ctype = char_type_node; + if (as != ADDR_SPACE_GENERIC) + ctype = build_qualified_type (ctype, ENCODE_QUAL_ADDR_SPACE (as)); exp = fold_build2 (MEM_REF, - build_array_type (char_type_node, + build_array_type (ctype, build_range_type (sizetype, size_one_node, len)), exp, build_int_cst (ptr_type_node, 0)); @@ -1381,7 +1385,7 @@ get_memory_rtx (tree exp, tree len) unsigned int align = get_pointer_alignment (TREE_OPERAND (exp, 0)); exp = build_fold_addr_expr (base); exp = fold_build2 (MEM_REF, - build_array_type (char_type_node, + build_array_type (ctype, build_range_type (sizetype, size_zero_node, NULL)),
next prev parent reply other threads:[~2023-12-04 9:07 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 [this message] 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-56J1LDYgqd@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).