public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100255] Crosscompiler to ia64-hp-vms: vmsdbgout.c:368:20: error: ISO C++17 does not allow 'register' storage class specifier [-Werror=register]
Date: Tue, 04 May 2021 12:26:44 +0000 [thread overview]
Message-ID: <bug-100255-4-NRhbX5GAzp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100255-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100255
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:2b8cc983060099f2bfbb21d42cf1aad4d55d2348
commit r8-10945-g2b8cc983060099f2bfbb21d42cf1aad4d55d2348
Author: Jakub Jelinek <jakub@redhat.com>
Date: Mon Apr 26 09:59:15 2021 +0200
vmsdbgout: Remove useless register keywords
register keyword was removed in C++17, and in vmsdbgout.c it served no
useful purpose.
2021-04-26 Jakub Jelinek <jakub@redhat.com>
PR debug/100255
* vmsdbgout.c (ASM_OUTPUT_DEBUG_STRING, vmsdbgout_begin_block,
vmsdbgout_end_block, lookup_filename, vmsdbgout_source_line):
Remove
register keywords.
(cherry picked from commit 297bfacdb448c0d29b8dfac2818350b90902bc75)
next prev parent reply other threads:[~2021-05-04 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 20:29 [Bug debug/100255] New: " jbglaw@lug-owl.de
2021-04-25 20:42 ` [Bug debug/100255] " jakub at gcc dot gnu.org
2021-04-26 8:00 ` [Bug target/100255] " cvs-commit at gcc dot gnu.org
2021-04-26 8:02 ` jakub at gcc dot gnu.org
2021-04-27 13:32 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:08 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:21 ` cvs-commit at gcc dot gnu.org
2021-05-04 12:26 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-11 14:29 ` pinskia at gcc dot gnu.org
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=bug-100255-4-NRhbX5GAzp@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).