public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67467] [5 Regression] Using "-Wall -Wextra -Wno-unused-dummy-argument" causes error
Date: Sun, 06 Sep 2015 10:05:00 -0000	[thread overview]
Message-ID: <bug-67467-4-Fl9f8em9q5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67467-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67467

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-09-06
            Summary|Using "-Wall -Wextra        |[5 Regression] Using "-Wall
                   |-Wno-unused-dummy-argument" |-Wextra
                   |causes error                |-Wno-unused-dummy-argument"
                   |                            |causes error
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
ICE confirmed for 5.2. It is fixed on trunk (6.0), and 4.9 gives

pr67467.f90:4:0: warning: unused parameter 'a' [-Wunused-parameter]
   INTEGER FUNCTION test( a )

IIRC there was some changes recently around 'unused-parameter' (parameter does
not have the same meaning in C and Fortran).


  reply	other threads:[~2015-09-06 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06  9:57 [Bug fortran/67467] New: " exodus6395 at gmail dot com
2015-09-06 10:05 ` dominiq at lps dot ens.fr [this message]
2015-09-06 16:22 ` [Bug fortran/67467] [5 Regression] " dominiq at lps dot ens.fr
2015-09-07 11:27 ` manu at gcc dot gnu.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=bug-67467-4-Fl9f8em9q5@http.gcc.gnu.org/bugzilla/ \
    --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).