From: Tom Tromey <tromey@redhat.com>
To: Neal Kruis <neal.kruis@bigladdersoftware.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: GDB Fortran 90 Support
Date: Mon, 17 Jun 2013 20:33:00 -0000 [thread overview]
Message-ID: <87ppvkbhpq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAOG8z536wLmh8zLcpHG=D0x7PmSu8JzuvyAyLEKvtHd=-F1qTw@mail.gmail.com> (Neal Kruis's message of "Wed, 12 Jun 2013 15:17:58 -0600")
>>>>> "Neal" == Neal Kruis <neal.kruis@bigladdersoftware.com> writes:
Neal> Can anyone tell me what the status is for Fortran 90+ support in GDB?
There is a branch to support VLAs, but it needs a rewrite.
I made a wiki page here as a placeholder; the current plan is described
in an email linked to from the page:
http://sourceware.org/gdb/wiki/FortranVLA
There are other open Fortran bugs. It gets a little maintenance from
time to time but nobody is very active on it right now.
Tom
next prev parent reply other threads:[~2013-06-17 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 21:18 Neal Kruis
2013-06-13 2:02 ` xunxun
2013-06-17 20:33 ` Tom Tromey [this message]
2013-06-18 5:09 ` xunxun
2013-06-18 17:14 ` Tom Tromey
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=87ppvkbhpq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=neal.kruis@bigladdersoftware.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