On Sun, Feb 10, 2019 at 03:51:01PM +0900, Masahiro Yamada wrote:
> I am still wondering,
> but if this is really worth doing in upstream code,
Yes, it is very worth doing it:
make <path-to-file>.s
is one of the basic steps one does when trying to pinpoint the Code:
line in a splat back to the code gcc generated.
> I think the following is a simpler idea.
Yes, you can do it this way too but I can't apply it here to play with
it because gmail probably corrupted the diff:
checking file Makefile
Hunk #1 FAILED at 729.
1 out of 1 hunk FAILED
checking file scripts/Makefile.build
patch: **** malformed patch at line 98: $(DISABLE_LTO) -fverbose-asm -S -o $@ $<
Please attach the diff or send it from another mail server.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
