From: Andrew Pinski <pinskia@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [pushed] wwwdocs: gcc-4.7: Adjust dwarfstd.org links
Date: Wed, 29 Mar 2023 15:40:15 -0700 [thread overview]
Message-ID: <CA+=Sn1nPx6-n6ys_QTVSGF=1Nquv7c-5rxPVgEF5hvmM8+X=YQ@mail.gmail.com> (raw)
In-Reply-To: <20230329220802.1F70133E56@hamza.pair.com>
On Wed, Mar 29, 2023 at 3:08 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> Business as usual - 301 Moved Permanently.
Just FYI, dwarfstd is now hosted by sourceware too. So I doubt these
URLs will change after this.
Thanks,
Andrew
>
> Gerald
> ---
> htdocs/gcc-4.7/changes.html | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/htdocs/gcc-4.7/changes.html b/htdocs/gcc-4.7/changes.html
> index f98f108c..91159f1f 100644
> --- a/htdocs/gcc-4.7/changes.html
> +++ b/htdocs/gcc-4.7/changes.html
> @@ -994,13 +994,13 @@ void set_portb (uint8_t value)
> GCC now supports various new GNU extensions to the DWARF debugging
> information format, like
> <a
> - href="https://www.dwarfstd.org/ShowIssue.php?issue=100909.1">entry
> + href="https://dwarfstd.org/issues/100909.1.html">entry
> value</a> and <a
> - href="https://www.dwarfstd.org/ShowIssue.php?issue=100909.2">call
> + href="https://dwarfstd.org/issues/100909.2.html">call
> site</a> information, <a
> - href="https://www.dwarfstd.org/ShowIssue.php?issue=140425.1">typed DWARF stack</a>
> + href="https://dwarfstd.org/issues/140425.1.html">typed DWARF stack</a>
> or <a
> - href="https://www.dwarfstd.org/ShowIssue.php?issue=110722.1">a
> + href="https://dwarfstd.org/issues/110722.1.html">a
> more compact macro representation</a>. Support for these extensions
> has been added to GDB 7.4. They can be disabled through the
> <code>-gstrict-dwarf</code> command-line option.
> --
> 2.39.2
next prev parent reply other threads:[~2023-03-29 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 22:07 Gerald Pfeifer
2023-03-29 22:40 ` Andrew Pinski [this message]
2023-03-30 10:39 ` Mark Wielaard
2023-03-30 23:12 ` Gerald Pfeifer
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='CA+=Sn1nPx6-n6ys_QTVSGF=1Nquv7c-5rxPVgEF5hvmM8+X=YQ@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).