From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: PATCH: PR testsuite/12040: GDB Fortran tests use g77 instead of gfortran
Date: Wed, 29 Jun 2011 17:52:00 -0000 [thread overview]
Message-ID: <BANLkTik5kVZOQ0hudSC--+Sv2B7jXD=SWA@mail.gmail.com> (raw)
In-Reply-To: <m3ei2czfw0.fsf@fleche.redhat.com>
On Wed, Jun 29, 2011 at 10:50 AM, Tom Tromey <tromey@redhat.com> wrote:
> H.J.> Did we get gfortran when searching for F77/f77 compiler?
>
> Tom> No, I forgot the most crucial bit :)
> Tom> I will write a follow-up patch to make our tests use gfortran.
> Tom> I don't think supporting g77 is all that worthwhile any more.
>
> Here is the follow-up. I am checking it in.
>
> This patch switches all the gdb.fortran tests to use the new gfortran
> support.
>
> Built and regested both locally and by the buildbot.
>
> Note that this introduces new FAILs:
>
> FAIL: gdb.fortran/array-element.exp: continue to breakpoint once again (the program exited)
> FAIL: gdb.fortran/array-element.exp: print the second element of array a
>
>
> These tests were previously not run, at least not on the machines I use.
> This is really just a single failure; I looked at it briefly and it is
> either a gfortran bug, or a bad assumption on the part of the testcase
> writer. I don't actually know Fortran so it is hard to say.
>
> Tom
>
> 2011-06-29 Tom Tromey <tromey@redhat.com>
>
> PR testsuite/12040:
> * gdb.fortran/array-element.exp: Use f90, not f77.
> * gdb.fortran/complex.exp: Use f90, not f77.
> * gdb.fortran/derived-type.exp: Use f90, not f77.
> * gdb.fortran/library-module.exp: Use f90, not f77.
> * gdb.fortran/logical.exp: Use f90, not f77.
> * gdb.fortran/module.exp: Use f90, not f77.
> * gdb.fortran/multi-dim.exp: Use f90, not f77.
> * gdb.fortran/subarray.exp: Use f90, not f77.
>
gfortran can be used as F77 compiler. Why not just return gfortran
for f77?
--
H.J.
next prev parent reply other threads:[~2011-06-29 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 18:24 H.J. Lu
2011-06-28 19:35 ` Tom Tromey
2011-06-28 19:56 ` H.J. Lu
2011-06-29 14:44 ` Tom Tromey
2011-06-29 14:51 ` H.J. Lu
2011-06-29 14:58 ` Tom Tromey
2011-06-29 17:50 ` Tom Tromey
2011-06-29 17:52 ` H.J. Lu [this message]
2011-06-29 18:26 ` Tom Tromey
2011-06-29 18:29 ` H.J. Lu
2011-06-30 13:29 ` Tom Tromey
2011-06-29 20:45 ` Jan Kratochvil
2011-06-29 20:49 ` Tom Tromey
2011-06-29 20:56 ` Jan Kratochvil
2011-06-29 16:10 ` Joel Brobecker
2011-06-29 17:35 ` Tom Tromey
2011-06-29 17:58 ` Joel Brobecker
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='BANLkTik5kVZOQ0hudSC--+Sv2B7jXD=SWA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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