From: Richard Biener via Gdb <gdb@sourceware.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Eric Botcazou <botcazou@adacore.com>,
Jason Merrill <jason@redhat.com>, Mark Wielaard <mark@klomp.org>,
gcc-patches@gcc.gnu.org,
Alexandra Petlanova Hajkova <ahajkova@redhat.com>,
gdb@sourceware.org, fortran@gcc.gnu.org
Subject: Re: [PATCH] dwarf2out: Emit DWARF 6 DW_AT_language_{name,version}
Date: Wed, 8 Jan 2025 10:09:24 +0100 (CET) [thread overview]
Message-ID: <4904089o-6986-9585-o15p-3pr19n506sqo@fhfr.qr> (raw)
In-Reply-To: <Z345TnQL8MqAm0MC@tucnak>
On Wed, 8 Jan 2025, Jakub Jelinek wrote:
> On Wed, Jan 08, 2025 at 09:14:59AM +0100, Eric Botcazou wrote:
> > > So, this patch is an alternative to the
> > > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/669671.html
> > > patch, which had the major problem that it required changing all the
> > > DWARF consumers to be able to debug C17 or later or C++17 or later
> > > sources.
> >
> > Do you plan to salvage the non-obsoleted parts of the above change?
>
> No. The switches on DW_AT_language value are a GCC internal thing,
> if we never generate say the post-DWARF5 DW_LANG_C_plus_plus_23,
> we don't need to handle it in the switch.
>
> Though, Ada and Fortran could have a similar change to the C/C++
> one, i.e. also add DW_AT_language_{name,version} for newer Ada and Fortran
> versions, say DW_LNAME_Ada and then dunno whether 2005, 2012 and 2022
> or 2007, 2012 and 2023, in https://dwarfstd.org/languages-v6.html
> the versioning scheme for Ada (as well as Fortran) is YYYY.
> Similarly DW_LNAME_Fortran 2018 and 2023.
>
> The reason I haven't done it myself is that the Ada FE doesn't tell
> Ada version at all - there is just "GNU Ada" and dwarf2out.cc right now
> implies it is Ada 95 for DWARF3 and Ada 83 otherwise.
> And in the Fortran case, while the FE provides a version, it only
> does so for Fortran 2003 and 2008 (and just "GNU Fortran" implies Fortran 90
> in dwarf2out). So, no marking of Fortran 2018 or Fortran 2023.
Btw, with DWARF only we now have the opportunity to add langhooks that
directly create DWARF DIEs or attributes (for early debug).
Richard.
next prev parent reply other threads:[~2025-01-08 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 19:22 Jakub Jelinek via Gdb
2025-01-08 7:18 ` Richard Biener via Gdb
2025-01-08 8:14 ` Eric Botcazou via Gdb
2025-01-08 8:37 ` Jakub Jelinek via Gdb
2025-01-08 8:51 ` Andre Vehreschild via Gdb
2025-01-08 9:09 ` Richard Biener via Gdb [this message]
2025-01-08 13:35 ` Mark Wielaard
2025-01-08 13:43 ` Jakub Jelinek via Gdb
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=4904089o-6986-9585-o15p-3pr19n506sqo@fhfr.qr \
--to=gdb@sourceware.org \
--cc=ahajkova@redhat.com \
--cc=botcazou@adacore.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=mark@klomp.org \
--cc=rguenther@suse.de \
/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