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/92183] gcc tries to create a relocation in a mergeable section
Date: Wed, 22 Dec 2021 09:49:56 +0000 [thread overview]
Message-ID: <bug-92183-4-3ciVR6e2Hn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92183-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92183
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |target
Target| |x86_64-linux-gnu
Keywords| |ra
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This seems like a register allocator issue also.
Before Register allocation we had:
(insn 14 2 15 2 (set (reg/f:DI 86)
(symbol_ref/f:DI ("*.LC1") [flags 0x2] <var_decl 0x7f7c225d32d0
*.LC1>)) "/app/example.cpp":8:14 76 {*movdi_internal}
(expr_list:REG_EQUIV (symbol_ref/f:DI ("*.LC1") [flags 0x2] <var_decl
0x7f7c225d32d0 *.LC1>)
(nil)))
(insn 15 14 7 2 (set (reg/f:DI 87)
(symbol_ref/f:DI ("*.LC0") [flags 0x2] <var_decl 0x7f7c225d3240
*.LC0>)) "/app/example.cpp":8:14 76 {*movdi_internal}
(expr_list:REG_EQUIV (symbol_ref/f:DI ("*.LC0") [flags 0x2] <var_decl
0x7f7c225d3240 *.LC0>)
(nil)))
(insn 7 15 8 2 (set (reg:V2DI 85)
(vec_concat:V2DI (reg/f:DI 87)
(reg/f:DI 86))) "/app/example.cpp":8:14 6752 {vec_concatv2di}
(expr_list:REG_DEAD (reg/f:DI 87)
(expr_list:REG_DEAD (reg/f:DI 86)
(expr_list:REG_EQUIV (vec_concat:V2DI (symbol_ref/f:DI ("*.LC0")
[flags 0x2] <var_decl 0x7f7c225d3240 *.LC0>)
(symbol_ref/f:DI ("*.LC1") [flags 0x2] <var_decl
0x7f7c225d32d0 *.LC1>))
(nil)))))
But after (LC1 is forced to memory):
(insn 15 14 17 2 (set (reg/f:DI 0 ax [87])
(symbol_ref/f:DI ("*.LC0") [flags 0x2] <var_decl 0x7fcc6368b240
*.LC0>)) "/app/example.cpp":8:14 76 {*movdi_internal}
(expr_list:REG_EQUIV (symbol_ref/f:DI ("*.LC0") [flags 0x2] <var_decl
0x7fcc6368b240 *.LC0>)
(nil)))
(insn 17 15 7 2 (set (reg/f:DI 20 xmm0 [87])
(reg/f:DI 0 ax [87])) "/app/example.cpp":8:14 76 {*movdi_internal}
(nil))
(insn 7 17 8 2 (set (reg:V2DI 20 xmm0 [85])
(vec_concat:V2DI (reg/f:DI 20 xmm0 [87])
(mem/u/c:DI (symbol_ref/u:DI ("*.LC2") [flags 0x2]) [0 S8 A64])))
"/app/example.cpp":8:14 6752 {vec_concatv2di}
(expr_list:REG_EQUIV (vec_concat:V2DI (symbol_ref/f:DI ("*.LC0") [flags
0x2] <var_decl 0x7fcc6368b240 *.LC0>)
(symbol_ref/f:DI ("*.LC1") [flags 0x2] <var_decl 0x7fcc6368b2d0
*.LC1>))
(nil)))
parent reply other threads:[~2021-12-22 9:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-92183-4@http.gcc.gnu.org/bugzilla/>]
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-92183-4-3ciVR6e2Hn@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: link
Be 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).