From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000 branch probability changes
Date: Fri, 30 Jun 2017 21:36:00 -0000 [thread overview]
Message-ID: <CAJA7tRYfCO7gRHGRxGGiYx8W3ajr32byoouPSMf6B2jswbpXJQ@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnyn9J43o0oQc7kwM87zFzyY+85q9WoZgh=yX=WVsye9Luw@mail.gmail.com>
On Fri, Jun 30, 2017 at 2:36 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> Convert the rs6000 port to use the new API for branch probabilities.
>
> Okay?
>
> Thanks, David
>
> * config/rs6000/rs6000.c (emit_unlikely_jump): Adjust to new branch
> probability data type.
>
> Index: rs6000.c
> ===================================================================
> --- rs6000.c (revision 249839)
> +++ rs6000.c (working copy)
> @@ -23514,10 +23514,9 @@
> static void
> emit_unlikely_jump (rtx cond, rtx label)
> {
> - int very_unlikely = REG_BR_PROB_BASE / 100 - 1;
> rtx x = gen_rtx_IF_THEN_ELSE (VOIDmode, cond, label, pc_rtx);
> rtx_insn *insn = emit_jump_insn (gen_rtx_SET (pc_rtx, x));
> - add_int_reg_note (insn, REG_BR_PROB, very_unlikely);
> + add_int_reg_note (insn, REG_BR_PROB, profile_probability::very_unlikely ());
Hmmm isn't this very unlikely to work :) ?
I used this as inspiration to do this for the arm ports but
add_int_reg_note expects an integer but very_unlikely returns
profile_probability ...
regards
Ramana
Ramana
> }
>
> /* A subroutine of the atomic operation splitters. Emit a load-locked
next prev parent reply other threads:[~2017-06-30 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 13:36 David Edelsohn
2017-06-30 21:36 ` Ramana Radhakrishnan [this message]
2017-06-30 23:18 ` Segher Boessenkool
2017-07-01 12:59 ` David Edelsohn
2017-07-01 13:06 ` Jan Hubicka
2017-07-01 13:19 ` David Edelsohn
2017-07-01 13:23 ` Jan Hubicka
2017-07-01 13:34 ` Jan Hubicka
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=CAJA7tRYfCO7gRHGRxGGiYx8W3ajr32byoouPSMf6B2jswbpXJQ@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).