From: Nathan Chancellor <nathan@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Fangrui Song <maskray@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
John Keeping <john@metanate.com>, Leo Yan <leo.yan@linaro.org>,
Michael Petlan <mpetlan@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Build perf with clang, failure with libperf
Date: Thu, 7 Apr 2022 08:03:53 -0700 [thread overview]
Message-ID: <Yk79WQQjvMyCddiO@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+icZUVKgLLJvNF6ZU1e7Hjr_FsJO7x0gsGL6Jje1nv2ukhueA@mail.gmail.com>
On Thu, Apr 07, 2022 at 12:27:14PM +0200, Sedat Dilek wrote:
> On Mon, Apr 4, 2022 at 11:53 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > Hi Arnaldo,
> >
> > On Mon, Apr 04, 2022 at 05:43:11PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Hi,
> > >
> > > Trying to apply Sedat's patch something changed in my system,
> > > and that patch wasn't enough, so I had to first apply this one:
> > >
> > > commit 173b552663419f40bcd3cf9df4f68285cac72727
> > > Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> > > Date: Mon Apr 4 17:28:48 2022 -0300
> > >
> > > tools build: Use $(shell ) instead of `` to get embedded libperl's ccopts
> > >
> > > Just like its done for ldopts and for both in tools/perf/Makefile.config.
> > >
> > > Using `` to initialize PERL_EMBED_CCOPTS somehow precludes using:
> > >
> > > $(filter-out SOMETHING_TO_FILTER,$(PERL_EMBED_CCOPTS))
> > >
> > > And we need to do it to allow for building with versions of clang where
> > > some gcc options selected by distros are not available.
> > >
> > > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > > Cc: Fangrui Song <maskray@google.com>
> > > Cc: Florian Fainelli <f.fainelli@gmail.com>
> > > Cc: Ian Rogers <irogers@google.com>
> > > Cc: Jiri Olsa <jolsa@kernel.org>
> > > Cc: John Keeping <john@metanate.com>
> > > Cc: Leo Yan <leo.yan@linaro.org>
> > > Cc: Michael Petlan <mpetlan@redhat.com>
> > > Cc: Namhyung Kim <namhyung@kernel.org>
> > > Cc: Nathan Chancellor <nathan@kernel.org>
> > > Cc: Nick Desaulniers <ndesaulniers@google.com>
> > > Cc: Sedat Dilek <sedat.dilek@gmail.com>
> > > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> > >
> > > diff --git a/tools/build/feature/Makefile b/tools/build/feature/Makefile
> > > index 1480910c792e2cb3..90774b60d31b2b8e 100644
> > > --- a/tools/build/feature/Makefile
> > > +++ b/tools/build/feature/Makefile
> > > @@ -217,7 +217,7 @@ strip-libs = $(filter-out -l%,$(1))
> > > PERL_EMBED_LDOPTS = $(shell perl -MExtUtils::Embed -e ldopts 2>/dev/null)
> > > PERL_EMBED_LDFLAGS = $(call strip-libs,$(PERL_EMBED_LDOPTS))
> > > PERL_EMBED_LIBADD = $(call grep-libs,$(PERL_EMBED_LDOPTS))
> > > -PERL_EMBED_CCOPTS = `perl -MExtUtils::Embed -e ccopts 2>/dev/null`
> > > +PERL_EMBED_CCOPTS = $(shell perl -MExtUtils::Embed -e ccopts 2>/dev/null)
> > > FLAGS_PERL_EMBED=$(PERL_EMBED_CCOPTS) $(PERL_EMBED_LDOPTS)
> > >
> > > $(OUTPUT)test-libperl.bin:
> > >
> > > ----------------------------------------------------- 8< -------------------
> > >
> > > After this I go on filtering out some of the gcc options that clang
> > > doesn't grok:
> > >
> > > diff --git a/tools/build/feature/Makefile b/tools/build/feature/Makefile
> > > index 90774b60d31b2b8e..bbc5e263e02385ed 100644
> > > --- a/tools/build/feature/Makefile
> > > +++ b/tools/build/feature/Makefile
> > > @@ -215,9 +215,12 @@ grep-libs = $(filter -l%,$(1))
> > > strip-libs = $(filter-out -l%,$(1))
> > >
> > > PERL_EMBED_LDOPTS = $(shell perl -MExtUtils::Embed -e ldopts 2>/dev/null)
> > > +PERL_EMBED_LDOPTS := $(filter-out -specs=%,$(PERL_EMBED_LDOPTS))
> > > PERL_EMBED_LDFLAGS = $(call strip-libs,$(PERL_EMBED_LDOPTS))
> > > PERL_EMBED_LIBADD = $(call grep-libs,$(PERL_EMBED_LDOPTS))
> > > PERL_EMBED_CCOPTS = $(shell perl -MExtUtils::Embed -e ccopts 2>/dev/null)
> > > +PERL_EMBED_CCOPTS := $(filter-out -ffat-lto-objects, $(PERL_EMBED_CCOPTS))
> > > +PERL_EMBED_CCOPTS := $(filter-out -specs=%,$(PERL_EMBED_CCOPTS))
> > > FLAGS_PERL_EMBED=$(PERL_EMBED_CCOPTS) $(PERL_EMBED_LDOPTS)
> > >
> > > $(OUTPUT)test-libperl.bin:
> > >
> > > ----------------------------------------------------- 8< -------------------
> > >
> > > And then get to the problems at the end of this message, which seem
> > > similar to the problem described here:
> > >
> > > From Nathan Chancellor <>
> > > Subject [PATCH] mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
> > >
> > > https://lkml.org/lkml/2020/9/1/135
> > >
> > > So perhaps in this case its better to disable that
> > > -Werror,-Wcompound-token-split-by-macro when building with clang?
> >
> > Yes, I think that is probably the best solution. As far as I can tell,
> > at least in this file and context, the warning appears harmless, as the
> > "create a GNU C statement expression from two different macros" is very
> > much intentional, based on the presence of PERL_USE_GCC_BRACE_GROUPS.
> > The warning is fixed in upstream Perl by just avoiding creating GNU C
> > statement expressions using STMT_START and STMT_END:
> >
> > https://github.com/Perl/perl5/issues/18780
> > https://github.com/Perl/perl5/pull/18984
> >
> > If I am reading the source code correctly, an alternative to disabling
> > the warning would be specifying -DPERL_GCC_BRACE_GROUPS_FORBIDDEN but it
> > seems like that might end up impacting more than just this site,
> > according to the issue discussion above.
> >
>
> Thanks for the pointer Nathan.
>
> As said I hit the problem with Debian's perl v5.34.
>
> Checking perl5 Git reveals:
>
> "skip using gcc brace groups for STMT_START/END"
> https://github.com/Perl/perl5/commit/7169efc77525df70484a824bff4ceebd1fafc760
GitHub says this is in 5.35.2, so it would make sense that 5.34 still
shows the issue.
> "Partially Revert "skip using gcc brace groups for STMT_START/END""
> https://github.com/Perl/perl5/commit/e08ee3cb66f362c4901846a46014cfdfcd60326c
>
> Perl v5.34.x seems not to have these changes:
> https://github.com/Perl/perl5/compare/v5.34.0...v5.34.1
>
> Unsure if there exists a real fix for perl5.
Perhaps those two changes could be cherry-picked into Debian's 5.34. I
have no idea if that is possible though.
Cheers,
Nathan
next prev parent reply other threads:[~2022-04-07 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 20:43 Arnaldo Carvalho de Melo
2022-04-04 21:53 ` Nathan Chancellor
2022-04-05 14:47 ` Arnaldo Carvalho de Melo
2022-04-05 15:46 ` Sedat Dilek
2022-04-05 20:00 ` Arnaldo Carvalho de Melo
2022-04-05 21:44 ` Arnaldo Carvalho de Melo
2022-04-06 20:44 ` Sedat Dilek
2022-04-08 14:49 ` Arnaldo Carvalho de Melo
2022-04-08 15:30 ` Sedat Dilek
2022-04-09 5:13 ` Sedat Dilek
2022-04-11 6:38 ` Sedat Dilek
2022-04-11 11:58 ` Greg Kroah-Hartman
2022-04-12 18:33 ` Sedat Dilek
2022-04-06 20:32 ` Sedat Dilek
2022-04-07 10:27 ` Sedat Dilek
2022-04-07 15:03 ` Nathan Chancellor [this message]
2022-04-07 16:25 ` Sedat Dilek
2022-04-07 17:10 ` Sedat Dilek
2022-04-07 17:42 ` Sedat Dilek
2022-04-07 17:14 ` Nathan Chancellor
2022-04-07 17:17 ` Sedat Dilek
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=Yk79WQQjvMyCddiO@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=f.fainelli@gmail.com \
--cc=irogers@google.com \
--cc=john@metanate.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maskray@google.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sedat.dilek@gmail.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
all inboxes | Powered by JetHome®