From: Richard Biener <rguenther@suse.de>
To: Rene Rebe <rene@exactcode.de>
Cc: gcc-patches@gcc.gnu.org, frank.scheiner@web.de
Subject: Re: [PATCH 2/3] Enabled LRA for ia64.
Date: Wed, 12 Jun 2024 13:01:23 +0200 (CEST) [thread overview]
Message-ID: <7osn6951-s8n4-7q7r-q872-11pr63q5202n@fhfr.qr> (raw)
In-Reply-To: <20240612.124242.1291436266291405210.rene@exactcode.de>
On Wed, 12 Jun 2024, Rene Rebe wrote:
>
> gcc/
> * config/ia64/ia64.cc: Enable LRA for ia64.
> * config/ia64/ia64.md: Likewise.
> * config/ia64/predicates.md: Likewise.
That looks simple enough. I cannot find any copyright assignment on
file with the FSF so you probably want to contribute to GCC under
the DCO (see https://gcc.gnu.org/dco.html), in that case please post
patches with Signed-off-by: tags.
For this patch please state how you tested it, I assume you
bootstrapped GCC natively on ia64-linux and ran the testsuite.
I can find two gcc-testresult postings, one appearantly with LRA
and one without? Both from May:
https://sourceware.org/pipermail/gcc-testresults/2024-May/816422.html
https://sourceware.org/pipermail/gcc-testresults/2024-May/816346.html
somehow for example libstdc++ summaries were not merged, it might
be you do not have recent python installed on the system? Or you
didn't use contrib/test_summary to create those mails. It would be
nice to see the difference between LRA and not LRA in the testresults,
can you quote that?
Thanks,
Richard.
> ---
> gcc/config/ia64/ia64.cc | 7 ++-----
> gcc/config/ia64/ia64.md | 4 ++--
> gcc/config/ia64/predicates.md | 2 +-
> 3 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/gcc/config/ia64/ia64.cc b/gcc/config/ia64/ia64.cc
> index ac3d56073ac..d189bfb2cb4 100644
> --- a/gcc/config/ia64/ia64.cc
> +++ b/gcc/config/ia64/ia64.cc
> @@ -618,9 +618,6 @@ static const scoped_attribute_specs *const ia64_attribute_table[] =
> #undef TARGET_LEGITIMATE_ADDRESS_P
> #define TARGET_LEGITIMATE_ADDRESS_P ia64_legitimate_address_p
>
> -#undef TARGET_LRA_P
> -#define TARGET_LRA_P hook_bool_void_false
> -
> #undef TARGET_CANNOT_FORCE_CONST_MEM
> #define TARGET_CANNOT_FORCE_CONST_MEM ia64_cannot_force_const_mem
>
> @@ -1329,7 +1326,7 @@ ia64_expand_move (rtx op0, rtx op1)
> {
> machine_mode mode = GET_MODE (op0);
>
> - if (!reload_in_progress && !reload_completed && !ia64_move_ok (op0, op1))
> + if (!lra_in_progress && !reload_completed && !ia64_move_ok (op0, op1))
> op1 = force_reg (mode, op1);
>
> if ((mode == Pmode || mode == ptr_mode) && symbolic_operand (op1, VOIDmode))
> @@ -1776,7 +1773,7 @@ ia64_expand_movxf_movrf (machine_mode mode, rtx operands[])
> }
> }
>
> - if (!reload_in_progress && !reload_completed)
> + if (!lra_in_progress && !reload_completed)
> {
> operands[1] = spill_xfmode_rfmode_operand (operands[1], 0, mode);
>
> diff --git a/gcc/config/ia64/ia64.md b/gcc/config/ia64/ia64.md
> index 698e302081e..d485acc0ea8 100644
> --- a/gcc/config/ia64/ia64.md
> +++ b/gcc/config/ia64/ia64.md
> @@ -2318,7 +2318,7 @@
> (match_operand:DI 3 "register_operand" "f"))
> (match_operand:DI 4 "nonmemory_operand" "rI")))
> (clobber (match_scratch:DI 5 "=f"))]
> - "reload_in_progress"
> + "lra_in_progress"
> "#"
> [(set_attr "itanium_class" "unknown")])
>
> @@ -3407,7 +3407,7 @@
> (match_operand:DI 2 "shladd_operand" "n"))
> (match_operand:DI 3 "nonmemory_operand" "r"))
> (match_operand:DI 4 "nonmemory_operand" "rI")))]
> - "reload_in_progress"
> + "lra_in_progress"
> "* gcc_unreachable ();"
> "reload_completed"
> [(set (match_dup 0) (plus:DI (mult:DI (match_dup 1) (match_dup 2))
> diff --git a/gcc/config/ia64/predicates.md b/gcc/config/ia64/predicates.md
> index 01a4effd339..85f5380e734 100644
> --- a/gcc/config/ia64/predicates.md
> +++ b/gcc/config/ia64/predicates.md
> @@ -347,7 +347,7 @@
> allows reload the opportunity to avoid spilling addresses to
> the stack, and instead simply substitute in the value from a
> REG_EQUIV. We'll split this up again when splitting the insn. */
> - if (reload_in_progress || reload_completed)
> + if (lra_in_progress || reload_completed)
> return true;
>
> /* Some symbol types we allow to use with any offset. */
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
next prev parent reply other threads:[~2024-06-12 11:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45833A6D-A84C-4276-AADB-BE2923886F64@exactcode.de>
[not found] ` <A935D68A-1B29-421A-A239-52CA50ADA239@suse.de>
[not found] ` <3DAB006A-ACE2-4BEC-AA01-87625DBEE259@exactcode.de>
2024-06-12 10:33 ` [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets Rene Rebe
2024-06-12 10:42 ` [PATCH 1/3] " Rene Rebe
2024-06-12 18:40 ` Jonathan Wakely
2024-06-12 18:48 ` Jonathan Wakely
2024-06-13 8:58 ` Gerald Pfeifer
2024-06-12 10:42 ` [PATCH 2/3] Enabled LRA for ia64 Rene Rebe
2024-06-12 11:01 ` Richard Biener [this message]
2024-06-12 12:50 ` René Rebe
2024-06-12 13:00 ` Richard Biener
2024-06-12 13:19 ` René Rebe
2024-06-12 14:03 ` Frank Scheiner
2024-06-12 14:09 ` Frank Scheiner
2024-06-12 18:54 ` Jonathan Wakely
2024-06-12 20:59 ` Frank Scheiner
2024-06-13 10:33 ` Jonathan Wakely
2024-06-13 14:11 ` Jeff Law
2024-06-13 14:16 ` Jonathan Wakely
2024-06-13 14:18 ` Jonathan Wakely
2024-06-14 11:07 ` Frank Scheiner
2024-06-14 12:53 ` Jonathan Wakely
2024-06-14 13:07 ` Frank Scheiner
2024-06-14 13:23 ` Jonathan Wakely
2024-06-17 18:03 ` Joseph Myers
2024-06-17 18:53 ` Jonathan Wakely
2024-06-17 19:36 ` Frank Scheiner
2024-06-13 7:02 ` Richard Biener
2024-06-12 10:43 ` [PATCH 3/3] MAINTAINERS: Add myself as IA-64 maintainer Rene Rebe
2024-06-12 19:03 ` Jonathan Wakely
2024-06-12 18:44 ` [PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets Jonathan Wakely
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=7osn6951-s8n4-7q7r-q872-11pr63q5202n@fhfr.qr \
--to=rguenther@suse.de \
--cc=frank.scheiner@web.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=rene@exactcode.de \
/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).