public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][www] Add note that STABS is deprecated
Date: Fri, 10 Sep 2021 09:36:53 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2109100936310.11781@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20210910073441.GA920497@tucnak>

On Fri, 10 Sep 2021, Jakub Jelinek wrote:

> On Fri, Sep 10, 2021 at 09:28:16AM +0200, Richard Biener via Gcc-patches wrote:
> > This amends the caveats section of the GCC 12 release notes according
> > to the STABS deprecation.
> > 
> > I'll wait with pushing to the point it reflects the state on trunk
> > rather than projecting what will be the state for GCC 12.
> 
> Most of the ports actually default to emit DWARF5, some DWARF4, some DWARF2,
> so perhaps better would be to emit DWARF (version 2 or later) debugging info?

True, I adjusted the change accordingly.

Thanks,
Richard.

> > diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
> > index 946faa49..c4a59c3b 100644
> > --- a/htdocs/gcc-12/changes.html
> > +++ b/htdocs/gcc-12/changes.html
> > @@ -47,6 +47,12 @@ a work-in-progress.</p>
> >      which still supports <code>-std=f95</code> and is recommended to be used
> >      instead in general.
> >    </li>
> > +  <li>
> > +    <strong>STABS:</strong>
> > +    Support for emitting the STABS debugging format is deprecated and will
> > +    be removed in the next release.  All ports now default to emit DWARF2
> > +    debugging info.
> > +  </li>
> >  </ul>
> >  
> >  
> > -- 
> > 2.31.1
> 
> 	Jakub
> 
> 

      reply	other threads:[~2021-09-10  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  7:28 Richard Biener
2021-09-10  7:34 ` Jakub Jelinek
2021-09-10  7:36   ` Richard Biener [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=nycvar.YFH.7.76.2109100936310.11781@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).