public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: Make driver process options with *.opt machinery
Date: Mon, 16 Aug 2010 10:07:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1008161005560.5708@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4C69056B.3050707@net-b.de>

On Mon, 16 Aug 2010, Tobias Burnus wrote:

>  On 08/12/2010 11:33 PM, Joseph S. Myers wrote:
> > Bootstrapped with no regressions on x86_64-unknown-linux-gnu.  OK to
> > commit?
> > 
> > fortran:
> > 2010-08-12  Joseph Myers<joseph@codesourcery.com>
> > 	* lang.opt (MDX, MMDX): Mark RejectDriver.
> 
> The Fortran bits are OK (Java and middle-end have been approved by others) - I
> think the Fortran changes are close to obvious.
> 
> However, I wonder about the following (cf. excerpt below), namely about the
> MissingArgError; shouldn't one use this for all *.opt files?

The awk scripts combine such settings from all .opt files.  In general, 
yes, it would be better for such combining not to be needed except for the 
flags saying what front ends an option is for, but I have not tried to fix 
existing .opt entries for that.

-- 
Joseph S. Myers
joseph@codesourcery.com

      reply	other threads:[~2010-08-16 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 21:34 Joseph S. Myers
2010-08-12 22:18 ` Richard Guenther
2010-08-16  9:31 ` Tobias Burnus
2010-08-16 10:07   ` Joseph S. Myers [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=Pine.LNX.4.64.1008161005560.5708@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    /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).