From: "Roger Sayle" <roger@nextmovesoftware.com>
To: "'GCC Patches'" <gcc-patches@gcc.gnu.org>
Cc: "'Segher Boessenkool'" <segher@kernel.crashing.org>,
"'Tom de Vries'" <tdevries@suse.de>
Subject: Re: [PATCH] Turn on LRA on all targets
Date: Sat, 29 Apr 2023 14:37:03 +0100 [thread overview]
Message-ID: <03ac01d97a9f$b0262960$10727c20$@nextmovesoftware.com> (raw)
Segher Boessenkool wrote:
> I send this patch now so that people can start testing.
>
> diff --git a/gcc/config/nvptx/nvptx.cc b/gcc/config/nvptx/nvptx.cc
> index 89349dae9e62..e32f17377525 100644
> --- a/gcc/config/nvptx/nvptx.cc
> +++ b/gcc/config/nvptx/nvptx.cc
> @@ -7601,9 +7601,6 @@ nvptx_asm_output_def_from_decls (FILE *stream, tree
name, tree value)
> #undef TARGET_ATTRIBUTE_TABLE
> #define TARGET_ATTRIBUTE_TABLE nvptx_attribute_table
>
>-#undef TARGET_LRA_P
>-#define TARGET_LRA_P hook_bool_void_false
>-
> #undef TARGET_LEGITIMATE_ADDRESS_P
> #define TARGET_LEGITIMATE_ADDRESS_P nvptx_legitimate_address_p
I've tested Segher's patch on nvptx-none with make and make -k check and
can confirm there are no new regressions. Nvptx is unique in that it
doesn't
use register allocation, i.e. GCC's only TARGET_NO_REGISTER_ALLOCATION
target,
so it's a little odd that it specifies which register allocator it doesn't
use.
I hope this helps,
Roger
--
next reply other threads:[~2023-04-29 13:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 13:37 Roger Sayle [this message]
2023-04-29 15:06 ` Jeff Law
2023-06-30 7:11 ` Flip the nvptx port to LRA (was: [PATCH] Turn on LRA on all targets) Thomas Schwinge
-- strict thread matches above, loose matches on Subject: below --
2023-04-23 16:47 [PATCH] Turn on LRA on all targets Segher Boessenkool
2023-04-23 17:01 ` Jeff Law
2023-04-23 20:23 ` Segher Boessenkool
2023-04-24 8:42 ` Andreas Schwab
2023-04-23 18:36 ` Paul Koning
2023-04-23 20:19 ` Segher Boessenkool
2023-04-23 18:56 ` Maciej W. Rozycki
2023-04-23 20:33 ` Segher Boessenkool
2023-05-15 21:09 ` Maciej W. Rozycki
2023-05-15 21:16 ` Sam James
2024-02-15 19:34 ` Sam James
2024-02-15 22:56 ` Segher Boessenkool
2024-02-16 1:41 ` Paul Koning
2024-02-16 10:22 ` Segher Boessenkool
2024-02-15 22:21 ` Paul Koning
2024-02-16 11:34 ` Maciej W. Rozycki
2024-02-16 13:47 ` Segher Boessenkool
2024-02-16 14:23 ` Maciej W. Rozycki
2024-02-16 14:31 ` Jakub Jelinek
2024-02-16 17:01 ` Maciej W. Rozycki
2024-02-17 0:38 ` Maciej W. Rozycki
2024-02-16 14:50 ` Paul Koning
2023-04-23 21:06 ` Uros Bizjak
2023-04-24 9:17 ` Segher Boessenkool
2023-04-24 9:46 ` Uros Bizjak
2023-04-29 14:38 ` Segher Boessenkool
2023-04-24 8:19 ` Richard Biener
2023-04-24 9:44 ` Segher Boessenkool
2023-04-30 19:52 ` Jeff Law
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='03ac01d97a9f$b0262960$10727c20$@nextmovesoftware.com' \
--to=roger@nextmovesoftware.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=tdevries@suse.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).