From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jiufu Guo <guojiufu@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com, linkw@gcc.gnu.org
Subject: Re: [PATCH V1] HIGH part of symbol ref is invalid for constant pool
Date: Tue, 26 Jul 2022 16:36:22 -0500 [thread overview]
Message-ID: <20220726213621.GB25951@gate.crashing.org> (raw)
In-Reply-To: <20220719143054.82832-1-guojiufu@linux.ibm.com>
Hi!
On Tue, Jul 19, 2022 at 10:30:54PM +0800, Jiufu Guo wrote:
> In patch https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597712.html,
> test case was not added. After more check, a testcase is added for it.
>
> The high part of the symbol address is invalid for the constant pool.
Invalid, how so? Is there a PR related here?
But it is not particularly useful ever, either: we do not know two
different addresses will have the same HIGH unless we know the exact
address, and then we don't need HIGH anyway.
> * config/rs6000/rs6000.cc (rs6000_cannot_force_const_mem):
> Return true for HIGH code rtx.
* config/rs6000/rs6000.cc (rs6000_cannot_force_const_mem): Return true
for HIGH code rtx.
Please don't wrap lines early: changelog lines are 80 positions long,
including the leading tab (which counts as eight positions).
> static bool
> rs6000_cannot_force_const_mem (machine_mode mode ATTRIBUTE_UNUSED, rtx x)
> {
> - if (GET_CODE (x) == HIGH
> - && GET_CODE (XEXP (x, 0)) == UNSPEC)
> + /* High part of a symbol ref/address can not be put into constant pool. e.g.
> + (high:DI (symbol_ref:DI ("var")..)) or
> + (high:DI (unspec:DI [(symbol_ref/u:DI ("*.LC0")..)
> + (high:DI (const:DI (plus:DI (symbol_ref:DI ("xx")) (const_int 12)))). */
> + if (GET_CODE (x) == HIGH)
> return true;
I'm not sure the new comment is helpful at all? Are these examples of
where the compiler (or assembler perhaps) will choke?
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/powerpc/constpoolcheck.c
> @@ -0,0 +1,11 @@
> +/* { dg-do compile { target powerpc*-*-* } } */
Everything in gcc.target/powerpc is target powerpc* always.
> +/* { dg-options "-O1 -mdejagnu-cpu=power10" } */
> +/* (high:DI (symbol_ref:DI ("var_48")..))) should not cause ICE. */
Ah, so there is an ICE, I see. Please open a PR, and mention that in
the testcase as well as in the commit message and changelog.
I agree with what the patch does, it just needs a little more work :-)
Segher
next prev parent reply other threads:[~2022-07-26 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 14:30 Jiufu Guo
2022-07-25 10:12 ` Kewen.Lin
2022-07-26 6:42 ` Jiufu Guo
2022-07-26 21:36 ` Segher Boessenkool [this message]
2022-07-28 12:53 ` Jiufu Guo
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=20220726213621.GB25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=linkw@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).