public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Why does GDB currently still supports only the features of Fortran 77 language?
Date: Mon, 11 Apr 2022 09:00:26 +0000	[thread overview]
Message-ID: <CY4PR1101MB2071AEFB30BD6DBE5B5EBBABB8EA9@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAGP6PO+EztyTuApKckh6uz3Yt5kDXfLt_3-sNMf0j_Ox06ar_A@mail.gmail.com>

Hi,

the documentation for the Fortran part of GDB is a bit outdated. It is not actually
true that GDB only supports Fortran 77 features - there is newer features that are
supported, too. Though there probably is not a standard (90/95..) for which one
could say that all Fortran features are fully supported (except maybe 77 though here
I am not sure).

GDB as of yet does not support every language feature of the latest standards.
As for the reason - GDB is a collaborative project that relies on contributions and
probably no one has come around doing the necessary work yet.

If you find that there is a specific feature missing, I would suggest opening a
'Feature request' bug for GDB at https://sourceware.org/bugzilla/ . Or, you could
become contributor yourself, too.

There is this patch I just sent that tries to improve the Fortran documentation a bit
https://sourceware.org/pipermail/gdb-patches/2022-April/187710.html
It describes all currently supported Fortran intrinsics.

Best regards,

Nils

> -----Original Message-----
> From: Gdb <gdb-bounces+nils-
> christian.kempke=intel.com@sourceware.org> On Behalf Of Hongyi Zhao via
> Gdb
> Sent: Saturday, April 9, 2022 3:23 AM
> To: gdb@sourceware.org
> Subject: Why does GDB currently still supports only the features of Fortran
> 77 language?
> 
> Nowadays, it is well known that Fortran 77 is a rather archaic and
> outdated Language, and it has been replicated by more modern Fortran
> versions, such as
> Fortran 90/95/2003/2008, and so on.
> 
> But in the documentation corresponding to the latest version of GDB
> [1], I noticed the following description, which surprised me quite a
> lot:
> 
> ```
> 15.4.6 Fortran
> 
> GDB can be used to debug programs written in Fortran, but it currently
> supports only the features of Fortran 77 language.
> ```
> 
> Today in the 21st century, why does GDB currently still supports only
> the features of Fortran 77 language?
> 
> [1]
> https://sourceware.org/gdb/current/onlinedocs/gdb/Fortran.html#Fortran
> 
> Best regards
> --
> Assoc. Prof. Hongsheng Zhao <hongyi.zhao@gmail.com>
> Theory and Simulation of Materials
> Hebei Vocational University of Technology and Engineering
> No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

      reply	other threads:[~2022-04-11  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09  1:23 Hongyi Zhao
2022-04-11  9:00 ` Kempke, Nils-Christian [this message]

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=CY4PR1101MB2071AEFB30BD6DBE5B5EBBABB8EA9@CY4PR1101MB2071.namprd11.prod.outlook.com \
    --to=nils-christian.kempke@intel.com \
    --cc=gdb@sourceware.org \
    --cc=hongyi.zhao@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).