public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kevinecahill at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61928] a fortran90 program compiles on hopper at NERSC but not under gfortran 4.9.0
Date: Sun, 27 Jul 2014 19:53:00 -0000 [thread overview]
Message-ID: <bug-61928-4-rRAuUmUdMJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61928-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61928
--- Comment #2 from Kevin Cahill <kevinecahill at gmail dot com> ---
Nonsense.
I included the linpack subroutines explicitly.
Look at my fortan code.
Best wishes,
Kevin
Kevin Cahill
Professor of Physics & Astronomy
Physics Dept. 1919 Lomas NE, MSC 07 4220
University of New Mexico
Albuquerque, NM 87131-0001
kevinecahill@gmail.com cahill@unm.edu 505 205 5448
On Jul 27, 2014, at 1:39 PM, pinskia at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61928
>
> Andrew Pinski <pinskia at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Version|unknown |4.9.0
>
> --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> You are not linking with the linpack library.
>
> --
> You are receiving this mail because:
> You reported the bug.
next parent reply other threads:[~2014-07-27 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-61928-4@http.gcc.gnu.org/bugzilla/>
2014-07-27 19:53 ` kevinecahill at gmail dot com [this message]
2014-07-27 21:10 ` jvdelisle at gcc dot gnu.org
2014-07-27 23:41 ` kevinecahill at gmail dot com
2014-08-02 14:41 ` dominiq at lps dot ens.fr
2014-08-02 15:56 ` jvdelisle at gcc dot gnu.org
2014-08-02 18:17 ` anlauf at gmx dot de
2014-12-06 14:55 ` dominiq at lps dot ens.fr
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-61928-4-rRAuUmUdMJ@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).