public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: rep.dot.nop@gmail.com
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] x86-64: Find a scratch register for large model profiling
Date: Fri, 2 Feb 2024 04:22:20 -0800	[thread overview]
Message-ID: <CAMe9rOp=ZxtmvOceQ2hnD5MVRqbZV=iEzejz9A2FQugSwj3VDg@mail.gmail.com> (raw)
In-Reply-To: <72D525E2-2F15-40FD-AA9A-4C334F8CB5FA@gmail.com>

On Fri, Feb 2, 2024 at 4:07 AM <rep.dot.nop@gmail.com> wrote:
>
> On 2 February 2024 00:02:54 CET, "H.J. Lu" <hjl.tools@gmail.com> wrote:
> >On Thu, Feb 1, 2024 at 10:32 AM Jakub Jelinek <jakub@redhat.com> wrote:
> >>
> >> On Thu, Feb 01, 2024 at 10:15:30AM -0800, H.J. Lu wrote:
> >> > --- a/gcc/config/i386/i386.cc
> >> > +++ b/gcc/config/i386/i386.cc
> >> > @@ -22749,6 +22749,31 @@ current_fentry_section (const char **name)
> >> >    return true;
> >> >  }
> >> >
> >> > +/* Return an unused caller-saved register at entry for profile.  */
> >> > +
> >> > +static int
> >> > +x86_64_select_profile_regnum (bool r11_ok ATTRIBUTE_UNUSED)
> >> > +{
> >> > +  int i;
> >>
> >> Why not just return R10_REG here if flag_entry != 0 (i.e. keep existing
> >> behavior unless emitting profiler after prologue)?
> >
> >Fixed in v2.
>
> Nit: r10_ok is now superfluous, but lets wait for Jakub.
> thanks

Fixed in v3.

Thanks.

-- 
H.J.

      reply	other threads:[~2024-02-02 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 18:15 H.J. Lu
2024-02-01 18:31 ` Jakub Jelinek
2024-02-01 23:02   ` H.J. Lu
2024-02-02 12:07     ` rep.dot.nop
2024-02-02 12:22       ` H.J. Lu [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='CAMe9rOp=ZxtmvOceQ2hnD5MVRqbZV=iEzejz9A2FQugSwj3VDg@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rep.dot.nop@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).