public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jlaw@tachyum.com>
To: "Martin Liška" <mliska@suse.cz>,
	"Jeff Law" <jeffreyalaw@gmail.com>,
	"Richard Biener" <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] Fix handling of flag_rename_registers.
Date: Sat, 16 Oct 2021 13:51:32 -0600	[thread overview]
Message-ID: <46d4b51b-3718-4af6-a2e5-2d47be479f10@tachyum.com> (raw)
In-Reply-To: <f2a2714f-503f-b71d-5ba9-b390c2e49ef4@suse.cz>



On 10/15/2021 9:27 AM, Martin Liška wrote:
> On 10/14/21 16:27, Jeff Law wrote:
>> So what's the preferred way to handle this?  We're in the process of 
>> evaluating -frename-registers on our target right now and subject to 
>> verification of a couple issues, our inclination is to turn it on for 
>> our target at -O2.
>>
>> Jeff
>
> I think the best approach is doing that in 
> TARGET_OPTION_OPTIMIZATION_TABLE like c6x does:
>
> static const struct default_options c6x_option_optimization_table[] =
>   {
>     { OPT_LEVELS_1_PLUS, OPT_frename_registers, NULL, 1 },
> ...
> }
ACK.  So nothing particularly special :-)

jeff

      reply	other threads:[~2021-10-16 19:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 12:17 Martin Liška
2021-10-12 13:37 ` Richard Biener
2021-10-12 14:03   ` Martin Liška
2021-10-12 15:11   ` Martin Liška
2021-10-13  8:39     ` Richard Biener
2021-10-13 10:02       ` Martin Liška
2021-10-13 11:49         ` Richard Biener
2021-10-14 14:27         ` Jeff Law
2021-10-15 15:27           ` Martin Liška
2021-10-16 19:51             ` Jeff Law [this message]

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=46d4b51b-3718-4af6-a2e5-2d47be479f10@tachyum.com \
    --to=jlaw@tachyum.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=joseph@codesourcery.com \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@gmail.com \
    /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).