From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Tristan Gingold <tgingold@free.fr>,
Douglas Rupp <douglas.b.rupp@gmail.com>,
rth@gcc.gnu.org
Subject: Re: [PATCH 1/3] STABS: remove -gstabs and -gxcoff functionality
Date: Mon, 5 Sep 2022 11:05:23 +0200 [thread overview]
Message-ID: <CAFiYyc3FYV-T1isAkTi8OujvxsZkOeBtDBReguO-D0oZibxwjg@mail.gmail.com> (raw)
In-Reply-To: <a37acfa1-2071-7e4a-e9a5-f09cd864553a@suse.cz>
On Mon, Sep 5, 2022 at 9:59 AM Martin Liška <mliska@suse.cz> wrote:
>
> On 9/2/22 10:54, Richard Biener wrote:
> > On Fri, Sep 2, 2022 at 9:00 AM Martin Liška <mliska@suse.cz> wrote:
> >>
> >> On 9/1/22 13:18, Richard Biener wrote:
> >>> I presume WarnRemoved will diagnose use of -gstabs but not fail
> >>> compilation. Will -gstabs then still enable -g (with the default debug
> >>> format)?
> >>
> >> No, it won't set -g option.
> >
> > That was the usual side-effect - I wonder if we want to emit extra
> > diagnostic when one of the obsolete options is given but -g is not
> > enabled in the end or whether we want to preserve the debug info
> > enablement effect?
>
> I would leave it for now and see if somebody would complain about
> the current behavior.
>
> >
> >>>
> >>> Please followup with a gcc-13/changes.html entry.
> >>
> >> Sure.
> >>
> >>>
> >>> I notice we have VMS_DEBUGGING_INFO left. From a quick look
> >>> it is used by alpha*-dec-* (exclusively) and ia64-hp-*vms* (maybe
> >>> also supports DWARF, it is ELF at least). One of the goals of
> >>> non-DWARF removal was to get rid of debug hooks and instead allow
> >>> "free-form" early debug generation from the frontends.
> >>
> >> Can you please explain what you mean by the free-form and what's expected
> >> to do with the VMS_DEBUGGING_INFO macro?
> >
> > Well, VMS debugging would go, just like STABS.
>
> Can go now, or shall we deprecate it in GCC 13 first?
Let's ask VMS maintainers - what's the state of DWARF support in VMS?
Is there active use of alpha*-dec-* or ia64-hp-*vms*?
> > With "free-form" I mean
> > that frontend code could call into the dwarf2out API directly, creating
> > DWARF DIEs for language specific info (we probably want to export more
> > and/or nicer APIs for such use).
>
> Ok, so bypassing dwarf2_debug_hooks, right? I can leave it to you such API
> improvement. What do you think?
Sure, it shouldn't be part of this series.
Richard.
> Cheers,
> Martin
>
> >
> > Richard.
> >
> >> Cheers,
> >> Martin
>
next prev parent reply other threads:[~2022-09-05 9:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 10:05 Martin Liška
2022-09-01 10:05 ` Martin Liška
2022-09-01 11:18 ` Richard Biener
2022-09-02 7:00 ` Martin Liška
2022-09-02 8:54 ` Richard Biener
2022-09-05 7:59 ` Martin Liška
2022-09-05 9:05 ` Richard Biener [this message]
2022-09-14 12:19 ` [COMMITTED] Fix unused variable warning (was: [PATCH 1/3] STABS: remove -gstabs and -gxcoff functionality) Jan-Benedict Glaw
2022-09-14 13:20 ` Martin Liška
2022-10-10 14:19 ` Restore default 'sorry' 'TARGET_ASM_CONSTRUCTOR', 'TARGET_ASM_DESTRUCTOR' " Thomas Schwinge
2022-10-10 14:23 ` Tom de Vries
2022-10-11 6:40 ` Richard Biener
2022-11-04 9:12 ` Better integrate default 'sorry' 'TARGET_ASM_CONSTRUCTOR', 'TARGET_ASM_DESTRUCTOR' (was: Restore default 'sorry' 'TARGET_ASM_CONSTRUCTOR', 'TARGET_ASM_DESTRUCTOR') Thomas Schwinge
2022-10-12 9:21 ` Restore default 'sorry' 'TARGET_ASM_CONSTRUCTOR', 'TARGET_ASM_DESTRUCTOR' (was: [PATCH 1/3] STABS: remove -gstabs and -gxcoff functionality) Martin Liška
2022-11-04 9:04 ` Thomas Schwinge
2022-11-04 9:07 ` Thomas Schwinge
2022-11-04 9:32 ` [PATCH 1/3] STABS: remove -gstabs and -gxcoff functionality Thomas Schwinge
2022-11-10 14:02 ` Martin Liška
2022-11-10 14:12 ` Michael Matz
2022-11-10 14:13 ` Martin Liška
2022-09-06 16:31 David Edelsohn
2022-09-06 17:00 ` David Edelsohn
2022-09-07 11:46 ` Martin Liška
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=CAFiYyc3FYV-T1isAkTi8OujvxsZkOeBtDBReguO-D0oZibxwjg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=douglas.b.rupp@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=rth@gcc.gnu.org \
--cc=tgingold@free.fr \
/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).