public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/23159] support -Wimplicit-fallthrough with clang
Date: Wed, 29 Nov 2023 23:28:30 +0000	[thread overview]
Message-ID: <bug-23159-4717-jiq3SZnc3I@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23159-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23159

--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d182e39881061b11d1eb85426d9a6953e3171bf5

commit d182e39881061b11d1eb85426d9a6953e3171bf5
Author: Tom Tromey <tom@tromey.com>
Date:   Sun Oct 15 11:09:07 2023 -0600

    Use C++17 [[fallthrough]] attribute

    This changes gdb to use the C++17 [[fallthrough]] attribute rather
    than special comments.

    This was mostly done by script, but I neglected a few spellings and so
    also fixed it up by hand.

    I suspect this fixes the bug mentioned below, by switching to a
    standard approach that, presumably, clang supports.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23159
    Approved-By: John Baldwin <jhb@FreeBSD.org>
    Approved-By: Luis Machado <luis.machado@arm.com>
    Approved-By: Pedro Alves <pedro@palves.net>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-11-29 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23159-4717@http.sourceware.org/bugzilla/>
2023-10-22 15:08 ` tromey at sourceware dot org
2023-11-29 23:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-29 23:29 ` tromey at sourceware dot 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-23159-4717-jiq3SZnc3I@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).