public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
	Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Subject: Re: [PATCH] Provide extension hint for aarch64 target (PR driver/83193).
Date: Wed, 01 Aug 2018 13:56:00 -0000	[thread overview]
Message-ID: <7a6072f7-86ec-f9a0-af5c-b89b47087fe8@suse.cz> (raw)
In-Reply-To: <37fcbcb3-eab3-9929-b84f-110c1646a717@suse.cz>

PING^1

On 07/18/2018 05:49 PM, Martin Liška wrote:
> Hi.
> 
> This patch improves aarch64 feature modifier hints.
> 
> May I please ask ARM folks to test the patch?
> Thanks,
> Martin
> 
> gcc/ChangeLog:
> 
> 2018-07-18  Martin Liska  <mliska@suse.cz>
> 
>         PR driver/83193
> 	* common/config/aarch64/aarch64-common.c (aarch64_parse_extension):
>         Set invalid_extension when there's any.
> 	(aarch64_get_all_extension_candidates): New function.
> 	(aarch64_rewrite_selected_cpu): Pass NULL as new argument.
> 	* config/aarch64/aarch64-protos.h (aarch64_get_all_extension_candidates):
>         Declare new function.
> 	* config/aarch64/aarch64.c (aarch64_parse_arch): Record
>         invalid_feature.
> 	(aarch64_parse_cpu): Likewise.
> 	(aarch64_print_hint_for_feature_modifier): New.
> 	(aarch64_validate_mcpu): Record invalid feature modifier
>         and print hint for it.
> 	(aarch64_validate_march): Likewise.
> 	(aarch64_handle_attr_arch): Likewise.
> 	(aarch64_handle_attr_cpu): Likewise.
> 	(aarch64_handle_attr_isa_flags): Likewise.
> 
> gcc/testsuite/ChangeLog:
> 
> 2018-07-18  Martin Liska  <mliska@suse.cz>
> 
>         PR driver/83193
> 	* gcc.target/aarch64/spellcheck_7.c: New test.
> 	* gcc.target/aarch64/spellcheck_8.c: New test.
> ---
>  gcc/common/config/aarch64/aarch64-common.c    | 20 +++++-
>  gcc/config/aarch64/aarch64-protos.h           |  4 +-
>  gcc/config/aarch64/aarch64.c                  | 67 +++++++++++++++----
>  .../gcc.target/aarch64/spellcheck_7.c         | 11 +++
>  .../gcc.target/aarch64/spellcheck_8.c         | 12 ++++
>  5 files changed, 97 insertions(+), 17 deletions(-)
>  create mode 100644 gcc/testsuite/gcc.target/aarch64/spellcheck_7.c
>  create mode 100644 gcc/testsuite/gcc.target/aarch64/spellcheck_8.c
> 
> 

  reply	other threads:[~2018-08-01 13:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 15:49 Martin Liška
2018-08-01 13:56 ` Martin Liška [this message]
2018-08-23 11:01   ` Martin Liška
2018-09-19 18:11     ` Martin Liška
2018-10-04  8:16       ` Martin Liška
2018-10-04 10:32 ` Kyrill Tkachov
2018-10-04 14:35   ` Martin Liška
2018-10-08 10:53   ` Martin Liška
2018-10-16 16:58     ` Kyrill Tkachov
2018-10-16 17:35     ` James Greenhalgh
2018-10-22 14:03       ` Martin Liška
2018-10-23 13:48         ` [PATCH] Remove extra memory allocation of strings Martin Liška
2018-11-01 10:13           ` Martin Liška
2018-11-08 12:20           ` Kyrill Tkachov
2018-11-08 15:22           ` James Greenhalgh
2018-10-23 19:02         ` [PATCH] Provide extension hint for aarch64 target (PR driver/83193) Martin Sebor
2018-10-24 11:48           ` Martin Liška
2018-10-24 19:28             ` Martin Sebor
2018-10-25 12:36               ` Martin Liška
2018-10-30 19:50                 ` James Greenhalgh

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=7a6072f7-86ec-f9a0-af5c-b89b47087fe8@suse.cz \
    --to=mliska@suse.cz \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.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).