From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jim Davis <jim.epost@gmail.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module
Date: Wed, 19 Oct 2016 22:03:47 +0000 [thread overview]
Message-ID: <20161019220346.GA20054@gate.crashing.org> (raw)
In-Reply-To: <CA+r1Zhiat4d8FqFcD1BBCxe5jyWOtSDZp99_CLV0qE1D3REquw@mail.gmail.com>
On Wed, Oct 19, 2016 at 12:51:44PM -0700, Jim Davis wrote:
> On Wed, Oct 19, 2016 at 12:25 AM, SF Markus Elfring
> <elfring@users.sourceforge.net> wrote:
> >
> > Are you interested that a software generation parameter like "-S"
> > (for output of assembler source files) could be directly supported
> > for a special build variant?
>
> No, if you want to see the assembly code then something like
>
> make defconfig; make EXTRA_CFLAGS="-g" drivers/md/; objdump -S
> drivers/md/whatever.o
>
> seems easy enough. You could write a little shell wrapper to save
> some keystrokes if you find you're running those commands frequently.
Don't forget -r when running objdump on an object file. But, you
want to use make drivers/md/whatever.s if you want to see the
assembler code.
And that doesn't work for build-time tools, which I think is what
the original discussion was about.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jim Davis <jim.epost@gmail.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation
Date: Wed, 19 Oct 2016 17:03:47 -0500 [thread overview]
Message-ID: <20161019220346.GA20054@gate.crashing.org> (raw)
In-Reply-To: <CA+r1Zhiat4d8FqFcD1BBCxe5jyWOtSDZp99_CLV0qE1D3REquw@mail.gmail.com>
On Wed, Oct 19, 2016 at 12:51:44PM -0700, Jim Davis wrote:
> On Wed, Oct 19, 2016 at 12:25 AM, SF Markus Elfring
> <elfring@users.sourceforge.net> wrote:
> >
> > Are you interested that a software generation parameter like "-S"
> > (for output of assembler source files) could be directly supported
> > for a special build variant?
>
> No, if you want to see the assembly code then something like
>
> make defconfig; make EXTRA_CFLAGS="-g" drivers/md/; objdump -S
> drivers/md/whatever.o
>
> seems easy enough. You could write a little shell wrapper to save
> some keystrokes if you find you're running those commands frequently.
Don't forget -r when running objdump on an object file. But, you
want to use make drivers/md/whatever.s if you want to see the
assembler code.
And that doesn't work for build-time tools, which I think is what
the original discussion was about.
Segher
next prev parent reply other threads:[~2016-10-19 22:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 13:54 Difficulties around "fixdep" for the usage of a kernel build output directory SF Markus Elfring
2016-10-18 15:12 ` Jim Davis
2016-10-18 16:38 ` SF Markus Elfring
2016-10-18 16:50 ` Jim Davis
2016-10-18 17:25 ` SF Markus Elfring
2016-10-18 20:44 ` Jim Davis
2016-10-19 7:25 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module SF Markus Elfring
2016-10-19 7:25 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring
2016-10-19 19:51 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module Jim Davis
2016-10-19 19:51 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation Jim Davis
2016-10-19 22:03 ` Segher Boessenkool [this message]
2016-10-19 22:03 ` Segher Boessenkool
2016-10-20 7:37 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module SF Markus Elfring
2016-10-20 7:37 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring
2016-10-20 6:33 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module SF Markus Elfring
2016-10-20 6:33 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring
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=20161019220346.GA20054@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=elfring@users.sourceforge.net \
--cc=jim.epost@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.