public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: [rhel dts libipt] Fix#2 [-Werror=implicit-fallthrough=] with gcc-7.1.1.
Date: Sat, 27 Jun 2026 23:58:15 GMT [thread overview]
Message-ID: <178260469565.1.587994695762337126.rpms-gdb-39868f207674@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 39868f2076745c7364e5a88f19091824c00c148b
Author : Jan Kratochvil <jan.kratochvil@redhat.com>
Date : 2017-06-09T15:45:38+02:00
Stats : +11/-4 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/gdb/c/39868f2076745c7364e5a88f19091824c00c148b?branch=gdb-17.2-rebase-f44
Log:
[rhel dts libipt] Fix#2 [-Werror=implicit-fallthrough=] with gcc-7.1.1.
---
diff --git a/gdb.spec b/gdb.spec
index 6840772..c15bfb9 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -26,7 +26,7 @@ Version: 8.0
# The release always contains a leading reserved number, start it at 1.
# `upstream' is not a part of `name' to stay fully rpm dependencies compatible for the testing.
-Release: 14%{?dist}
+Release: 15%{?dist}
License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and LGPLv3+ and BSD and Public Domain and GFDL
Group: Development/Debuggers
@@ -1615,6 +1615,9 @@ then
fi
%changelog
+* Fri Jun 9 2017 Jan Kratochvil <jan.kratochvil@redhat.com> - 8.0-15.fc26
+- [rhel dts libipt] Fix#2 [-Werror=implicit-fallthrough=] with gcc-7.1.1.
+
* Fri Jun 9 2017 Jan Kratochvil <jan.kratochvil@redhat.com> - 8.0-14.fc26
- [rhel dts libipt] Fix [-Werror=implicit-fallthrough=] with gcc-7.1.1.
diff --git a/v1.6.1-implicit-fallthrough.patch b/v1.6.1-implicit-fallthrough.patch
index f2ddb4f..db844d3 100644
--- a/v1.6.1-implicit-fallthrough.patch
+++ b/v1.6.1-implicit-fallthrough.patch
@@ -7,13 +7,17 @@ gcc-7.1.1-1.fc27.x86_64
case ptbq_decode: {
^~~~
---- processor-trace-1.6.1-orig/libipt/src/pt_block_decoder.c 2017-05-31 13:30:32.000000000 +0200
-+++ processor-trace-1.6.1/libipt/src/pt_block_decoder.c 2017-06-09 07:24:12.644587611 +0200
-@@ -2324,6 +2324,7 @@ static int pt_blk_proceed_no_event_cache
+diff --git a/libipt/src/pt_block_decoder.c b/libipt/src/pt_block_decoder.c
+index 21783a6..91d5bb3 100644
+--- a/libipt/src/pt_block_decoder.c
++++ b/libipt/src/pt_block_decoder.c
+@@ -2095,6 +2095,9 @@ static int pt_blk_proceed_no_event_cached(struct pt_block_decoder *decoder,
}
/* Fall through to ptbq_decode. */
++#if __GNUC__ >= 7
+ __attribute__ ((fallthrough));
++#endif
case ptbq_decode: {
struct pt_insn_ext iext;
reply other threads:[~2026-06-27 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178260469565.1.587994695762337126.rpms-gdb-39868f207674@fedoraproject.org \
--to=jan.kratochvil@redhat.com \
--cc=git-commits@fedoraproject.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