public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "toon at moene dot indiv dot nluug dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/13464] New: [gfortran options] -d8, -i8 and -r8 not passed correctly to compiler proper.
Date: Mon, 22 Dec 2003 12:03:00 -0000	[thread overview]
Message-ID: <20031222115039.13464.toon@moene.indiv.nluug.nl> (raw)

The Fortran options -d8, -i8 and -r8 are not passed to f951 correctly.

The option processor thinks that -d8 is a form of the -d dump options, in spite
of the fact that there is no such  -d8 option.  -i8 is simply consumed without
ever resurfacing. -r8 is simply an `unrecognized option'.

I tried to debug this, but got lost in all the routines that look at or mangle
the options.  However, one thing is clear:

In options.c we find:

  { "-d8",
    N_("Set the default real and integer kinds to double precision"),
    OPT_d, 2, CL_F95 | CL_REJECT_NEGATIVE },
    ^^^^^ this is wrong.

-- 
           Summary: [gfortran options] -d8, -i8 and -r8 not passed correctly
                    to compiler proper.
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: driver
        AssignedTo: neil at daikokuya dot co dot uk
        ReportedBy: toon at moene dot indiv dot nluug dot nl
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13464


             reply	other threads:[~2003-12-22 11:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22 12:03 toon at moene dot indiv dot nluug dot nl [this message]
2003-12-22 17:08 ` [Bug driver/13464] " pinskia at gcc dot gnu dot org
2003-12-22 20:49 ` neil at daikokuya dot co dot uk
2003-12-22 23:40 ` toon at moene dot indiv dot nluug dot nl
2003-12-23  0:00 ` pinskia at gcc dot gnu dot org
2003-12-23  9:02 ` neil at daikokuya dot co dot uk
2003-12-23 14:33 ` toon at moene dot indiv dot nluug dot nl
2003-12-24  2:39 ` neil at daikokuya dot co dot uk
2003-12-24  2:40 ` toon at moene dot indiv dot nluug dot nl
2003-12-24 14:53 ` neil at daikokuya dot co dot uk
2004-01-11  9:10 ` neil at gcc dot gnu dot org
2004-03-03  3:47 ` [Bug fortran/13464] [gfortran options] " pinskia at gcc dot gnu dot org
2004-03-03  6:53 ` steven at gcc dot gnu dot org
2004-08-25 13:04 ` [Bug fortran/13464] " c dot lemmen at fz-juelich dot de
2004-11-21 16:18 ` pinskia at gcc dot gnu dot org
2005-01-07 21:58 ` [Bug driver/13464] " toon at moene dot indiv dot nluug dot nl
2005-02-20  9:33 ` [Bug driver/13464] -i8 and -r8 not passed correctly to compiler proper. and -d8 does not work pinskia at gcc dot gnu dot org
2005-02-22 21:40 ` pinskia at gcc dot gnu dot org
2005-03-08 23:52 ` sgk at troutmask dot apl dot washington dot edu
2005-03-08 23:53 ` sgk at troutmask dot apl dot washington dot edu
2005-03-11  5:31 ` wilson at gcc dot gnu dot org
2005-04-21  5:04 ` mmitchel at gcc dot gnu dot org
2005-04-21  5:29 ` pinskia at gcc dot gnu dot org

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=20031222115039.13464.toon@moene.indiv.nluug.nl \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).