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 c++/60994] gcc does not recognize hidden/shadowed enumeration as valid nested-name-specifier Date: Sat, 02 Dec 2023 11:16:35 +0000 [thread overview] Message-ID: <bug-60994-4-aiYlA8cUOs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60994-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60994 --- Comment #19 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>: https://gcc.gnu.org/g:193ef02a7f4f3e5349ad9cf8d3d4df466a99b677 commit r14-6075-g193ef02a7f4f3e5349ad9cf8d3d4df466a99b677 Author: Roger Sayle <roger@nextmovesoftware.com> Date: Sat Dec 2 11:15:14 2023 +0000 RISC-V: Improve style to work around PR 60994 in host compiler. This simple patch allows me to build a cross-compiler to riscv using older versions of RedHat's system compiler. The issue is PR c++/60994 where g++ doesn't like the same name (demand_flags) to be used by both a variable and a (enumeration) type, which is also undesirable from a (GNU) coding style perspective. One solution is to rename the type to demand_flags_t, but a less invasive change is to simply use another identifier for the problematic local variable, renaming demand_flags to dflags. 2023-12-02 Roger Sayle <roger@nextmovesoftware.com> gcc/ChangeLog * config/riscv/riscv-vsetvl.cc (csetvl_info::parse_insn): Rename local variable from demand_flags to dflags, to avoid conflicting with (enumeration) type of the same name.
prev parent reply other threads:[~2023-12-02 11:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-29 7:00 [Bug c++/60994] New: " momchil.velikov at gmail dot com 2014-04-29 7:07 ` [Bug c++/60994] " trippels at gcc dot gnu.org 2014-04-29 7:56 ` redi at gcc dot gnu.org 2014-04-29 9:59 ` momchil.velikov at gmail dot com 2014-08-28 19:02 ` aaw at gcc dot gnu.org 2015-02-12 13:49 ` redi at gcc dot gnu.org 2015-02-12 13:53 ` jakub at gcc dot gnu.org 2015-02-12 14:28 ` momchil.velikov at gmail dot com 2015-04-14 15:30 ` jason at gcc dot gnu.org 2021-08-04 21:03 ` pinskia at gcc dot gnu.org 2021-08-04 21:04 ` pinskia at gcc dot gnu.org 2023-12-02 11:16 ` cvs-commit at gcc dot gnu.org [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=bug-60994-4-aiYlA8cUOs@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: linkBe 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).