public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Quentin Monnet <quentin@isovalent.com>
To: Thomas Richter <tmricht@linux.ibm.com>,
	broonie@kernel.org, hca@linux.ibm.com, sfr@canb.auug.org.au,
	liam.howlett@oracle.com, acme@redhat.com, ast@kernel.org,
	bpf@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] bpftool: fix broken compile on s390 for linux-next repository
Date: Tue, 18 Apr 2023 10:13:29 +0100	[thread overview]
Message-ID: <51f19356-2a42-bb2d-7d4f-275fe334f73a@isovalent.com> (raw)
In-Reply-To: <20230418085516.1104514-1-tmricht@linux.ibm.com>

2023-04-18 10:55 UTC+0200 ~ Thomas Richter <tmricht@linux.ibm.com>
> Commit 9fd496848b1c ("bpftool: Support inline annotations when dumping the CFG of a program")
> breaks the build of the perf tool on s390 in the linux-next repository.
> Here is the make output:
> 
> make -C tools/perf
> ....
> btf_dumper.c: In function 'dotlabel_puts':
> DEBUG: btf_dumper.c:838:25: error: '__fallthrough' undeclared \
> 		(first use in this function); did you mean 'fallthrough'?
> DEBUG:   838 |                         __fallthrough;
> DEBUG:       |                         ^~~~~~~~~~~~~
> DEBUG:       |                         fallthrough
> DEBUG: btf_dumper.c:838:25: note: each undeclared identifier is reported \
> 		only once for each function it appears in
> DEBUG: btf_dumper.c:837:25: warning: this statement may fall through \
>                 [-Wimplicit-fallthrough=]
> DEBUG:   837 |                         putchar('\\');
> DEBUG:       |                         ^~~~~~~~~~~~~
> DEBUG: btf_dumper.c:839:17: note: here
> DEBUG:   839 |                 default:
> DEBUG:       |                 ^~~~~~~
> DEBUG: make[3]: *** [Makefile:247: /builddir/build/BUILD/kernel-6.2.fc37/\
> 		        linux-6.2/tools/perf/util/bpf_skel/ \
> 		        .tmp/bootstrap/btf_dumper.o] Error 1
> 
> The compile fails because symbol __fallthrough unknown, but symbol
> fallthrough is known and works fine.
> 
> Fix this and replace __fallthrough by fallthrough.
> 
> With this change, the compile works.
> 
> Output after:
> 
>  # make -C tools/perf
>  ....
>  CC      util/bpf-filter.o
>  CC      util/bpf-filter-flex.o
>  LD      util/perf-in.o
>  LD      perf-in.o
>  LINK    perf
>  make: Leaving directory '/root/mirror-linux-next/tools/perf'
>  #
> 
> Fixes: 9fd496848b1c ("bpftool: Support inline annotations when dumping the CFG of a program")
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>

(Repost from
https://lore.kernel.org/all/20230412123636.2358949-1-tmricht@linux.ibm.com)

Acked-by: Quentin Monnet <quentin@isovalent.com>


  reply	other threads:[~2023-04-18  9:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  8:55 [PATCH] bpftool: fix broken compile on s390 for linux-next repository Thomas Richter
2023-04-18  9:13 ` Quentin Monnet [this message]
2023-04-19 14:50 ` Daniel Borkmann
2023-04-20  0:39   ` Quentin Monnet
  -- strict thread matches above, loose matches on Subject: below --
2023-04-12 12:36 Thomas Richter
2023-04-12 13:27 ` Quentin Monnet
2023-04-14  8:47   ` Heiko Carstens
2023-04-14 16:53     ` Mark Brown
2023-04-14 16:58       ` Quentin Monnet

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=51f19356-2a42-bb2d-7d4f-275fe334f73a@isovalent.com \
    --to=quentin@isovalent.com \
    --cc=acme@redhat.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=broonie@kernel.org \
    --cc=hca@linux.ibm.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tmricht@linux.ibm.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