From: Trond Myklebust <trondmy@primarydata.com>
To: "linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"elfring@users.sourceforge.net" <elfring@users.sourceforge.net>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: Difficulties for compilation without extra optimisation
Date: Sun, 3 Dec 2017 15:17:32 +0000 [thread overview]
Message-ID: <1512314250.3673.6.camel@primarydata.com> (raw)
In-Reply-To: <a2ac6d05-fdd6-82bb-075e-b7eb81b516fe@users.sourceforge.net>
On Sun, 2017-12-03 at 15:15 +0100, SF Markus Elfring wrote:
> 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@users
> .sourceforge.net>;
>
> 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?
I'm not seeing anything obviously wrong with the NFS use of tracepoints
there, and the warning suggests rather that gcc has an issue with the
inlined assembly code in jump_label.h.
Ccing Peter Zijlstra (who appears to have been the last person to touch
that assembly code) and Steven Rostedt.
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com
next prev parent reply other threads:[~2017-12-03 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:53 [PATCH RFC v1] nfs/write: Use common error handling code in nfs_lock_and_join_requests() SF Markus Elfring
2017-12-03 14:15 ` Difficulties for compilation without extra optimisation SF Markus Elfring
2017-12-03 15:17 ` Trond Myklebust [this message]
2017-12-03 21:22 ` Steven Rostedt
2017-12-03 21:56 ` SF Markus Elfring
2017-12-04 2:40 ` Steven Rostedt
2017-12-04 9:55 ` SF Markus Elfring
2017-12-04 9:00 ` SF Markus Elfring
2017-12-04 9:48 ` Steven Rostedt
2017-12-04 10:18 ` 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=1512314250.3673.6.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox