public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Evandro Menezes <e.menezes@samsung.com>
Cc: "'gcc-patches'" <gcc-patches@gcc.gnu.org>,
	       "'Marcus Shawcroft'" <Marcus.Shawcroft@arm.com>,
	       "'Kyrill Tkachov'" <kyrylo.tkachov@arm.com>,
	       Andrew Pinski <pinskia@gmail.com>
Subject: Re: [PATCH 1/4][AArch64] Add scheduling and cost models for Exynos M1
Date: Thu, 05 Nov 2015 09:22:00 -0000	[thread overview]
Message-ID: <20151105092243.GA31968@arm.com> (raw)
In-Reply-To: <563A92DF.7070009@samsung.com>

On Wed, Nov 04, 2015 at 05:21:03PM -0600, Evandro Menezes wrote:
> Please, ignore the previous patch.  This is the intended patch.
> 
> Sorry.
> 
> -- 
> Evandro Menezes
> 
> On 11/04/2015 05:18 PM, Evandro Menezes wrote:
> >This patch adds extra tuning information about AArch64 targets:
> >
> > * Maximum number of case values before resorting to a jump table
> >   The default values assumed independently of the specific backends
> >   may be rather low for modern processors, which sport quite efficient
> >   direct branch prediction, whereas indirect branch prediction is
> >   still typically not so efficient.  This value may be specifically
> >   set for a processor or left at zero to use the default values.
> > * L1 cache line size
> >   The auto-prefetcher uses this information when emitting software
> >   prefetch insns.
> >
> >Please, commit if it's alright.
> >
> >Thank you,
> >
> 

Thanks for the patch,

> diff --git a/gcc/config/aarch64/aarch64-protos.h b/gcc/config/aarch64/aarch64-protos.h
> index 81792bc..ecf4685 100644
> --- a/gcc/config/aarch64/aarch64-protos.h
> +++ b/gcc/config/aarch64/aarch64-protos.h
> @@ -195,6 +195,9 @@ struct tune_params
>    int vec_reassoc_width;
>    int min_div_recip_mul_sf;
>    int min_div_recip_mul_df;
> +  int max_case_values; /* Case values threshold; or 0 for the default.  */

If we're using an int, how about -1 as the sentinel value? (Maybe someone
really likes jump tables!). Otherwise, make this an unsigned int?

> +
> +  int cache_line_size; /* Cache line size; or 0 for the default.  */

unsigned int?

The patch is otherwise OK, though it needs a ChangeLog.

Thanks,
James

  reply	other threads:[~2015-11-05  9:22 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 23:38 [AArch64] " Evandro Menezes
2015-10-28 10:40 ` James Greenhalgh
2015-10-28 10:45   ` Andrew Pinski
2015-10-28 21:58     ` Evandro Menezes
2015-10-29 23:02   ` Evandro Menezes
2015-10-28 11:01 ` Kyrill Tkachov
2015-10-29 19:38   ` Evandro Menezes
2015-11-04 23:10 ` [PATCH 0/4][AArch64] " Evandro Menezes
2015-11-04 23:18   ` [PATCH 1/4][AArch64] " Evandro Menezes
2015-11-04 23:21     ` Evandro Menezes
2015-11-05  9:22       ` James Greenhalgh [this message]
2015-11-05 17:31         ` Evandro Menezes
2015-11-12 14:47           ` James Greenhalgh
2015-11-05 20:51   ` [PATCH 2/4][AArch64] Increase the loop peeling limit Evandro Menezes
2015-11-19 22:04     ` Evandro Menezes
2015-11-20 11:53       ` James Greenhalgh
2015-12-03 21:07         ` Evandro Menezes
2015-12-14 11:26           ` James Greenhalgh
2015-12-15 23:34             ` Evandro Menezes
2015-12-16 11:24               ` Richard Earnshaw (lists)
2015-12-16 12:42                 ` Richard Biener
2015-12-16 20:11                 ` Evandro Menezes
2016-01-08 22:55                   ` Evandro Menezes
2016-02-03 19:46                     ` Evandro Menezes
2016-03-16 19:48                       ` Evandro Menezes
2015-11-05 23:30   ` [PATCH 3/4][AArch64] Add scheduling model for Exynos M1 Evandro Menezes
2015-11-05 23:30   ` Evandro Menezes
2015-11-09 23:06     ` Evandro Menezes
2015-11-10 17:50       ` [PATCH 3a/4][AArch64] Add attribute for compatibility with ARM pipeline models Evandro Menezes
2015-11-10 18:01         ` Ramana Radhakrishnan
2015-11-10 18:03           ` Ramana Radhakrishnan
2015-11-12 14:55         ` James Greenhalgh
2015-11-12 15:39           ` Evandro Menezes
2015-11-12 17:32             ` Evandro Menezes
2015-11-19 22:05               ` Evandro Menezes
2015-11-20 12:27               ` James Greenhalgh
2015-11-20 14:34                 ` Kyrill Tkachov
2015-11-20 15:56                   ` Evandro Menezes
2015-11-20 15:55                 ` Evandro Menezes
2015-11-20 16:16                   ` James Greenhalgh
2015-11-10 17:54       ` [PATCH 3b/4][AArch64] Add scheduling model for Exynos M1 Evandro Menezes
2015-11-19 22:06         ` Evandro Menezes
2015-11-20 17:17         ` James Greenhalgh
2015-11-20 22:07           ` Evandro Menezes
2015-12-03 20:58           ` Evandro Menezes
2015-12-04  9:25             ` Kyrill Tkachov
2015-12-07 19:55               ` Evandro Menezes
2015-11-06  0:09   ` [PATCH 4/4][AArch64] Add cost " Evandro Menezes
2015-11-19 22:06     ` Evandro Menezes
2015-11-20 17:19       ` James Greenhalgh
2015-11-24  9:56     ` Kyrill Tkachov
2015-12-03 20:49     ` Evandro Menezes

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=20151105092243.GA31968@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=e.menezes@samsung.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@arm.com \
    --cc=pinskia@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).