From: Borislav Petkov <bp@alien8.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] kbuild: Disable extra debugging info in .s output
Date: Wed, 6 Feb 2019 11:47:29 +0100 [thread overview]
Message-ID: <20190206104729.GC7314@zn.tnic> (raw)
In-Reply-To: <20190202144227.GC27822@zn.tnic>
On Sat, Feb 02, 2019 at 03:42:27PM +0100, Borislav Petkov wrote:
> On Sat, Feb 02, 2019 at 10:48:00PM +0900, Masahiro Yamada wrote:
> > '?=' is the same as '=' here.
>
> Sure but if the slowdown disappears, then make does something else for
> '?=' apparently vs for '='.
Ok, let me ask a different question then: would a separate target which
will be used to generate only clean asm for debugging purposes ala
make <path-to-file>.asm
or so be an acceptable approach?
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-02-06 10:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 9:53 [PATCH] kbuild: Disable extra debugging info in .s output Borislav Petkov
2019-01-31 11:58 ` Borislav Petkov
2019-02-01 3:06 ` Masahiro Yamada
2019-02-01 9:42 ` Borislav Petkov
2019-02-01 10:09 ` Masahiro Yamada
2019-02-01 10:23 ` Borislav Petkov
2019-02-01 11:03 ` Masahiro Yamada
2019-02-01 10:30 ` Borislav Petkov
2019-02-01 10:36 ` Borislav Petkov
2019-02-01 11:58 ` Masahiro Yamada
2019-02-01 15:11 ` Borislav Petkov
2019-02-02 13:48 ` Masahiro Yamada
2019-02-02 14:42 ` Borislav Petkov
2019-02-06 10:47 ` Borislav Petkov [this message]
2019-02-10 6:51 ` Masahiro Yamada
2019-02-10 12:39 ` Borislav Petkov
2019-02-18 8:30 ` Borislav Petkov
2019-02-18 9:10 ` Masahiro Yamada
2019-02-18 14:31 ` Borislav Petkov
2019-02-19 23:55 ` Masahiro Yamada
2019-02-01 10:51 ` 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=20190206104729.GC7314@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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.