On Fri, Jan 29, 2021 at 11:31 PM Nick Desaulniers <ndesaulniers@xxxxxxxxxx> wrote: > > On Fri, Jan 29, 2021 at 2:23 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > > > On Fri, Jan 29, 2021 at 11:21 PM Nick Desaulniers > > <ndesaulniers@xxxxxxxxxx> wrote: > > > > > > On Fri, Jan 29, 2021 at 2:11 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > > > > > > > On Fri, Jan 29, 2021 at 11:09 PM Nick Desaulniers > > > > <ndesaulniers@xxxxxxxxxx> wrote: > > > > > > > > > > On Fri, Jan 29, 2021 at 1:20 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > > > > > > > > > > > On Fri, Jan 29, 2021 at 10:13 PM Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > > > > > > > > > > > > > > On Fri, Jan 29, 2021 at 10:09 PM Nick Desaulniers > > > > > > > <ndesaulniers@xxxxxxxxxx> wrote: > > > > > > > > > > > > > > > > Can you tell me please what is the precise command line invocation of > > > > > > > > make and which source file you observed this on so that I can > > > > > > > > reproduce? > > > > > > > > > > If you don't send me your invocation of `make`, I cannot help you. > > > > > > > > > > > > > /usr/bin/perf_5.10 stat make V=1 -j4 LLVM=1 LLVM_IAS=1 > > > > PAHOLE=/opt/pahole/bin/pahole LOCALVERSION=-10-amd64-clang12 > > > > -lto-pgo KBUILD_VERBOSE=1 KBUILD_BUILD_HOST=iniza > > > > KBUILD_BUILD_USER=sedat.dilek@xxxxxxxxx > > > > KBUILD_BUILD_TIMESTAMP=2021-01-29 bindeb-pkg > > > > KDEB_PKGVERSION=5.11.0~rc5-10~bullseye+dileks1 > > > > > > $ make LLVM=1 LLVM_IAS=1 -j72 defconfig > > > $ make LLVM=1 LLVM_IAS=1 -j72 menuconfig > > > <enable CONFIG_DEBUG_INFO and CONFIG_DEBUG_INFO_DWARF5> > > > $ make LLVM=1 LLVM_IAS=1 -j72 V=1 &> log.txt > > > $ grep '\-g -gdwarf-5 -g -gdwarf-5' log.txt | wc -l > > > 0 > > > $ grep '\-g -gdwarf-5' log.txt | wc -l > > > 2517 > > > > > > Do have the patch applied twice, perhaps? > > > > > > > Switched to my v6 local Git branch and invoked above make line I gave you. > > I still see that double. > > Looks like I need some "undrunken" switch. > > Can you follow my steps precisely to see whether it's your .config? > Perhaps there is a config that duplicates DEBUG_CFLAGS that is not set > in the defconfig? If so, it's still harmless to specify the same > commands twice, and likely isn't introduced by this patch set if so; > so I'm not sure how much more effort is worth pursuing. > If I follow your steps of make I do not see it "double" (in my local v6 Git branch). Looks like this is coming from my build-script. I checked if I have some double dwarf(-5) patches double - Nope. - Sedat -
