public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/3] STABS: remove -gstabs and -gxcoff functionality
Date: Fri, 2 Sep 2022 09:00:04 +0200	[thread overview]
Message-ID: <c71c4339-ef23-f321-95da-e696e6a24e79@suse.cz> (raw)
In-Reply-To: <CAFiYyc17oLEmrkMBrezM30m3-a2yBtLyoDe9AVGEo-1EuD2E0g@mail.gmail.com>

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.

> 
> 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?

Cheers,
Martin

  reply	other threads:[~2022-09-02  7:00 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 [this message]
2022-09-02  8:54     ` Richard Biener
2022-09-05  7:59       ` Martin Liška
2022-09-05  9:05         ` Richard Biener
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=c71c4339-ef23-f321-95da-e696e6a24e79@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@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).