From: James Greenhalgh <james.greenhalgh@arm.com>
To: Kyrill Tkachov <kyrylo.tkachov@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][AArch64][3/14] Refactor option override code
Date: Mon, 03 Aug 2015 09:59:00 -0000 [thread overview]
Message-ID: <20150803095943.GA8841@arm.com> (raw)
In-Reply-To: <55B1F59A.9010309@arm.com>
On Fri, Jul 24, 2015 at 09:21:46AM +0100, Kyrill Tkachov wrote:
>
> Thanks for the review, here's an updated version.
> In the end, I chose to retain the use alloca (other patches in the series
> are reworked to use it too).
>
> How's this?
A nit or two from code you were moving or that got caught up in the diff,
but otherwise OK to commit with the issues highlighted below fixed up.
>
> - aarch64_build_bitmask_table ();
> +/* Validate a command-line -mcpu option. Parse the cpu and extensions (if any)
> + specified in STR and throw errors if appropriate. Put the results if
> + they are valid in RES and ISA_FLAGS. */
> +static void
> +aarch64_validate_mcpu (const char *str, const struct processor **res,
> + unsigned long *isa_flags)
Newline between comment and function.
> +/* Validate a command-line -march option. Parse the arch and extensions
> + (if any) specified in STR and throw errors if appropriate. Put the
> + results, if they are valid, in RES and ISA_FLAGS. */
> +static void
> +aarch64_validate_march (const char *str, const struct processor **res,
> + unsigned long *isa_flags)
And here.
> +/* Validate a command-line -mtune option. Parse the cpu
> + specified in STR and throw errors if appropriate. Put the
> + result, if it is valid, in RES. */
> +static void
> +aarch64_validate_mtune (const char *str, const struct processor **res)
And here.
Thanks,
James
prev parent reply other threads:[~2015-08-03 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:21 Kyrill Tkachov
2015-07-20 16:58 ` James Greenhalgh
2015-07-24 8:30 ` Kyrill Tkachov
2015-08-03 9:59 ` James Greenhalgh [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=20150803095943.GA8841@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@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).