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/60898] model compile error with gfortran 4.7 and gcc 4.9 on Mac OS 10.9
Date: Mon, 21 Apr 2014 13:02:00 -0000 [thread overview]
Message-ID: <bug-60898-4-GQR8zLRwDn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60898-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60898
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2014-04-21
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Did you
See <http://gcc.gnu.org/bugs.html> for instructions.
?
Apparently not. You have to provide the code for plib8b.f90 (along with files
for needed modules and includes). Note that it will help if you can reduce the
code.
next prev parent reply other threads:[~2014-04-21 13:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 3:06 [Bug fortran/60898] New: " shaojuncycle at gmail dot com
2014-04-21 13:02 ` dominiq at lps dot ens.fr [this message]
2014-04-23 1:49 ` [Bug fortran/60898] " shaojuncycle at gmail dot com
2014-04-23 2:49 ` jvdelisle at gcc dot gnu.org
2014-05-02 10:30 ` dominiq at lps dot ens.fr
2014-07-13 12:51 ` dominiq at lps dot ens.fr
2014-07-13 12:55 ` dominiq at lps dot ens.fr
2014-07-13 21:51 ` jvdelisle at gcc dot gnu.org
2014-07-15 16:17 ` dominiq at lps dot ens.fr
2014-07-15 16:31 ` [Bug fortran/60898] [4.8/4.9/4.10 Regression] model compile error with gfortran 4.7 and gcc 4.9 dominiq at lps dot ens.fr
2014-07-15 16:34 ` dominiq at lps dot ens.fr
2014-07-15 18:03 ` anlauf at gmx dot de
2014-11-19 13:28 ` [Bug fortran/60898] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2014-12-01 11:57 ` rguenth at gcc dot gnu.org
2014-12-01 22:30 ` burnus at gcc dot gnu.org
2014-12-19 13:35 ` jakub at gcc dot gnu.org
2015-02-10 14:34 ` jvdelisle at gcc dot gnu.org
2015-02-10 15:25 ` mikael at gcc dot gnu.org
2015-02-14 15:27 ` mikael at gcc dot gnu.org
2015-02-14 15:42 ` dominiq at lps dot ens.fr
2015-02-14 19:00 ` mikael at gcc dot gnu.org
2015-02-15 10:45 ` dominiq at lps dot ens.fr
2015-02-16 14:13 ` mikael at gcc dot gnu.org
2015-03-08 11:53 ` mikael at gcc dot gnu.org
2015-03-12 16:09 ` mikael at gcc dot gnu.org
2015-03-12 17:59 ` mikael 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-60898-4-GQR8zLRwDn@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).