Hello, I came along some software modules where I suggested source code adjustments. Example: nfs/write: Use common error handling code in nfs_lock_and_join_requests() https://lkml.org/lkml/2017/11/7/599 https://patchwork.kernel.org/patch/10047013/ https://lkml.kernel.org/r/<7f072f78-eef4-6d87-d233-cee71dac5a32@xxxxxxxxxxxxxxxxxxxxx> I would like to check corresponding build results then without extra optimisation applied by the compiler. But I got surprised by error messages for a command like the following. elfring@Sonne:~/Projekte/Linux/next-patched> my_cc=/usr/bin/gcc-7 && LANG=C make -j4 CC="${my_cc}" HOSTCC="${my_cc}" EXTRA_CFLAGS='-O0' allmodconfig fs/nfs/write.o … In file included from ./include/linux/compiler.h:58:0, from ./include/uapi/linux/stddef.h:1, from ./include/linux/stddef.h:4, from ./include/uapi/linux/posix_types.h:4, from ./include/uapi/linux/types.h:13, from ./include/linux/types.h:5, from fs/nfs/write.c:9: ./arch/x86/include/asm/jump_label.h: In function ‘trace_nfs_writeback_page_enter’: ./include/linux/compiler-gcc.h:275:38: warning: asm operand 0 probably doesn’t match constraints #define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0) … How do you think about to improve this software situation anyhow? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
