From mboxrd@z Thu Jan 1 00:00:00 1970 From: Segher Boessenkool Date: Wed, 19 Oct 2016 22:03:47 +0000 Subject: Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module Message-Id: <20161019220346.GA20054@gate.crashing.org> List-Id: References: <4f2251fc-94ee-41d3-cc03-a39cee5a084c@users.sourceforge.net> <1238ba8e-a297-6de5-2e6a-50e6e72e77d3@users.sourceforge.net> <4fe8b518-6145-5322-a852-beeb61abd559@users.sourceforge.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jim Davis Cc: SF Markus Elfring , linux-kbuild@vger.kernel.org, Michal Marek , linux-kernel , kernel-janitors@vger.kernel.org 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 > 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