public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@net-b.de>
To: "Joseph S. Myers" <joseph@codesourcery.com>
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 09:31:00 -0000	[thread overview]
Message-ID: <4C69056B.3050707@net-b.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1008122131420.28932@digraph.polyomino.org.uk>

  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?

Tobias

> +++ gcc-mainline/gcc/c-family/c.opt	2010-08-12 02:48:01.000000000 -0700
> MDX
> -C ObjC C++ ObjC++ Separate MissingArgError(missing filename after %qs)
> +C ObjC C++ ObjC++ RejectDriver Separate MissingArgError(missing filename after %qs)

> +++ gcc-mainline/gcc/fortran/lang.opt	2010-08-12 02:48:14.000000000 -0700
>   MDX
> -Fortran Separate
> +Fortran Separate RejectDriver

> +++ gcc-mainline/gcc/java/lang.opt	2010-08-12 02:47:21.000000000 -0700
>   MD_
> -Java Undocumented
> +Java Undocumented RejectDriver

  parent reply	other threads:[~2010-08-16  9:31 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 [this message]
2010-08-16 10:07   ` Joseph S. Myers

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=4C69056B.3050707@net-b.de \
    --to=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-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).