public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66605] -Wunused-parameter causes internal compiler error with gfortran 5.1.0
Date: Wed, 24 Jun 2015 20:42:00 -0000	[thread overview]
Message-ID: <bug-66605-4-9PtpChIb93@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66605-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #9)
> I still think this is a latent bug in the way that Fortran is generating the
> PARAM_DECL for time, but if the Fortran maintainers are not interested in
> investigating that, then I could prepare a patch with any of the
> work-arounds I have proposed above as soon as a Fortran maintainer (someone
> that will approve the patch) chooses one.

Scratch that. Since the goal is to bluntly silence the warning, then the only
work-around I see is the one proposed in the previous comment. 

(It would be interesting to know at which GCC version or revision the warning
started appearing).
>From gcc-bugs-return-490128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 24 21:24:50 2015
Return-Path: <gcc-bugs-return-490128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3617 invoked by alias); 24 Jun 2015 21:24:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3572 invoked by uid 48); 24 Jun 2015 21:24:46 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/58133] GCC should emit arm assembly following the unified syntax
Date: Wed, 24 Jun 2015 21:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-58133-4-dEAEVhAk6Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-06/txt/msg02460.txt.bz2
Content-length: 528

https://gcc.gnu.org/bugzilla/show_bug.cgi?idX133

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ramana at gcc dot gnu.org

--- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
Thumb1 Fixed for 5.0 with Terry's work - see release notes
https://gcc.gnu.org/gcc-5/changes.html


ARM state is a bit more involved.


  parent reply	other threads:[~2015-06-24 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 19:11 [Bug fortran/66605] New: " kyle.niemeyer at gmail dot com
2015-06-19 19:25 ` [Bug fortran/66605] " kyle.niemeyer at gmail dot com
2015-06-20 16:50 ` manu at gcc dot gnu.org
2015-06-24 18:48 ` manu at gcc dot gnu.org
2015-06-24 19:00 ` dominiq at lps dot ens.fr
2015-06-24 19:16 ` manu at gcc dot gnu.org
2015-06-24 19:38 ` dominiq at lps dot ens.fr
2015-06-24 20:37 ` manu at gcc dot gnu.org
2015-06-24 20:42 ` manu at gcc dot gnu.org [this message]
2015-06-25  7:12 ` dominiq at lps dot ens.fr
2015-06-25  9:00 ` manu at gcc dot gnu.org
2015-06-25  9:41 ` dominiq at lps dot ens.fr
2015-06-26 16:46 ` manu at gcc dot gnu.org
2015-06-29 16:26 ` 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-66605-4-9PtpChIb93@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).