From: Arvind Sankar <nivedita@alum.mit.edu>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
Masahiro Yamada <masahiroy@kernel.org>,
Fangrui Song <maskray@google.com>,
Rong Chen <rong.a.chen@intel.com>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Makefile: Improve compressed debug info support detection
Date: Thu, 11 Jun 2020 17:44:13 -0400 [thread overview]
Message-ID: <20200611214413.GA3924125@rani.riverdale.lan> (raw)
In-Reply-To: <CAKwvOd=UyEPOx5M0w+uwiYwE5fY-A5vDmuvPnWs_pK4zW4RH-w@mail.gmail.com>
On Thu, Jun 11, 2020 at 01:44:53PM -0700, Nick Desaulniers wrote:
> On Wed, Jun 10, 2020 at 4:39 PM Arvind Sankar <nivedita@alum.mit.edu> wrote:
> >
> > On Wed, Jun 10, 2020 at 07:30:46PM -0400, Arvind Sankar wrote:
> > > On Wed, Jun 10, 2020 at 02:27:55PM -0700, Nick Desaulniers wrote:
> > >
> > > No, as-option does invoke the assembler. The problem here is that with
> > > -Wa, the option is only seen by the assembler, not the gcc driver. So it
> > > will succeed because the assembler supports it, but it will not test
> > > whether the gcc driver also supports it.
> > >
> >
> > I think in theory another way to fix it is to just use -Wa even for
> > CFLAGS, assuming the compiler itself doesn't have to do anything with
> > the option and it's purely an assembler thing. Then you'd just do the as
> > and ld tests.
>
> I don't think the CFLAGS are used for .S source files though. We may
> drive assembler via the compiler, but AFLAGS are used in place of
> CFLAGS IIRC. (eh, maybe not for ARCH=arc, ARCH=sh, ARCH=csky,
> ARCH=mips)
>
> --
> Thanks,
> ~Nick Desaulniers
I meant just replace
KBUILD_CFLAGS += -gz=zlib
with
KBUILD_CFLAGS += -Wa,--compress-debug-sections=zlib
leaving KBUILD_AFLAGS the same as before
KBUILD_AFLAGS += -Wa,--compress-debug-sections=zlib
This would avoid depending on the subtleties in the gcc driver's support
for this option. But -gz=zlib is passed to cc1 as well as the assembler,
so I'm not sure if there would be some loss from not passing it to the
compiler.
next prev parent reply other threads:[~2020-06-11 21:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 13:11 gcc-5: error: -gz is not supported in this configuration kernel test robot
2020-06-09 17:28 ` Nick Desaulniers
2020-06-09 17:49 ` Fangrui Song
2020-06-10 0:30 ` [kbuild-all] " Rong Chen
2020-06-10 0:58 ` Fangrui Song
2020-06-10 1:49 ` Rong Chen
2020-06-10 3:12 ` Arvind Sankar
2020-06-10 3:23 ` Arvind Sankar
2020-06-10 4:26 ` Arvind Sankar
2020-06-10 6:37 ` Fangrui Song
2020-06-10 19:11 ` [PATCH] Makefile: Improve compressed debug info support detection Arvind Sankar
2020-06-10 21:27 ` Nick Desaulniers
2020-06-10 23:30 ` Arvind Sankar
2020-06-10 23:39 ` Arvind Sankar
2020-06-11 20:44 ` Nick Desaulniers
2020-06-11 21:44 ` Arvind Sankar [this message]
2020-06-11 21:09 ` Nick Desaulniers
2020-06-11 21:52 ` Arvind Sankar
2020-06-11 22:03 ` [PATCH v2] " Arvind Sankar
2020-06-11 23:38 ` Nick Desaulniers
2020-06-14 2:21 ` Masahiro Yamada
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=20200611214413.GA3924125@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=ndesaulniers@google.com \
--cc=rong.a.chen@intel.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;
as well as URLs for NNTP newsgroup(s).