public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Jim Wilson <jim.wilson@linaro.org>
Cc: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, <nd@arm.com>
Subject: Re: [PATCH, ARM/AArch64] drop aarch32 support for falkor/qdf24xx
Date: Mon, 12 Jun 2017 10:40:00 -0000	[thread overview]
Message-ID: <20170612104000.GA38916@arm.com> (raw)
In-Reply-To: <CABXYE2WrqwzT4=J+BjAvbAGZwzKG83KMZ96uU1ycq6Lx6uFfHQ@mail.gmail.com>

On Fri, Jun 09, 2017 at 01:03:34PM -0700, Jim Wilson wrote:
>  # Arch Matches
> Index: gcc/doc/invoke.texi
> ===================================================================
> --- gcc/doc/invoke.texi	(revision 249025)
> +++ gcc/doc/invoke.texi	(working copy)
> @@ -13983,8 +13983,8 @@ processors implementing the target architecture.
>  Specify the name of the target processor for which GCC should tune the
>  performance of the code.  Permissible values for this option are:
>  @samp{generic}, @samp{cortex-a35}, @samp{cortex-a53}, @samp{cortex-a57},
> -@samp{cortex-a72}, @samp{cortex-a73}, @samp{exynos-m1}, @samp{falkor},
> -@samp{qdf24xx}, @samp{xgene1}, @samp{vulcan}, @samp{thunderx},
> +@samp{cortex-a72}, @samp{cortex-a73}, @samp{exynos-m1},
> +@samp{xgene1}, @samp{vulcan}, @samp{thunderx},
>  @samp{thunderxt88}, @samp{thunderxt88p1}, @samp{thunderxt81},
>  @samp{thunderxt83}, @samp{thunderx2t99}, @samp{cortex-a57.cortex-a53},
>  @samp{cortex-a72.cortex-a53}, @samp{cortex-a73.cortex-a35},

In both the original patch, and the backport, you're modifying the
AArch64 options here. I'd expect the edits to be to the AArch32 options
(these start somewhere around line 15,000).

Thanks,
James

  parent reply	other threads:[~2017-06-12 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  3:52 Jim Wilson
2017-05-24 14:12 ` Richard Earnshaw (lists)
2017-05-24 14:20   ` Jim Wilson
2017-05-24 15:20     ` Richard Earnshaw (lists)
2017-05-24 16:05       ` Jim Wilson
2017-05-24 16:30         ` Richard Earnshaw (lists)
2017-05-25  9:29           ` Richard Earnshaw (lists)
2017-06-09 20:03             ` Jim Wilson
2017-06-10  9:44               ` Richard Earnshaw (lists)
2017-06-12 10:40               ` James Greenhalgh [this message]
2017-06-23 21:46                 ` Jim Wilson

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=20170612104000.GA38916@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jim.wilson@linaro.org \
    --cc=nd@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).