public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Add ToLower .opt facility
Date: Mon, 04 Apr 2011 09:14:00 -0000	[thread overview]
Message-ID: <4D998BE7.4020709@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1104020022110.32286@digraph.polyomino.org.uk>

Hi Joseph,

> This patch adds a ToLower .opt feature, for option arguments that are
> case-insensitive and should be converted to a canonical lowercase
> form.
>
> This is relevant to at least mips, mn10300 and rx.  This patch makes
> rx use it, thereby causing an existing spec that tested only for a
> lowercase option form to start to work correctly with both variants
> (since specs only need to match canonical options).

Thanks!

> Bootstrapped with no regressions on x86_64-unknown-linux-gnu, and
> tested building cc1 and xgcc for cross to rx-elf.  Will commit to
> trunk in the absence of target maintainer objections.

No objections and definite approval from me.

> 2011-04-01  Joseph Myers<joseph@codesourcery.com>
>
> 	* doc/options.texi (ToLower): Document.
> 	* opt-functions.awk (switch_bit_fields): Initialize cl_tolower
> 	field.
> 	* opts-common.c (decode_cmdline_option): Handle cl_tolower.
> 	* opts.h (cl_option): Add cl_tolower field.
> 	* config/rx/rx.c (rx_handle_option): Use strcmp of -mcpu=
> 	arguments with lowercase strings.
> 	* config/rx/rx.opt (mcpu=): Add ToLower.
> 	* config/rx/t-rx (MULTILIB_MATCHES): Don't handle uppercase -mcpu=
> 	argument.

Cheers
   Nick

      reply	other threads:[~2011-04-04  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02  0:23 Joseph S. Myers
2011-04-04  9:14 ` Nick Clifton [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=4D998BE7.4020709@redhat.com \
    --to=nickc@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.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).