From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: next-20200528 - build error in kernel/rcu/refperf.c
Date: Fri, 29 May 2020 00:16:31 -0400 [thread overview]
Message-ID: <538911.1590725791@turing-police> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
commit 9088b449814f788d24f35a5840b6b2c2a23cd32a
Author: Paul E. McKenney <paulmck@kernel.org>
Date: Mon May 25 17:22:24 2020 -0700
refperf: Provide module parameter to specify number of experiments
changes this line of code (line 389)
- reader_tasks[exp].result_avg = 1000 * process_durations(exp) / ((exp + 1) * loops);
+ result_avg[exp] = 1000 * process_durations(nreaders) / (nreaders * loops);
On a 32-bit ARM make allmodconfig with gcc 8.3, this results in:
ERROR: modpost: "__aeabi_uldivmod" [kernel/rcu/refperf.ko] undefined!
make[1]: *** [scripts/Makefile.modpost:103: __modpost] Error 1
I admit not understanding why the original line of code worked and the new one doesn't.
Maybe gcc is smarter/dumber about the ranges of 'exp' and 'nreaders' than we thought?
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2020-05-29 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 4:16 Valdis Klētnieks [this message]
2020-05-29 4:48 ` next-20200528 - build error in kernel/rcu/refperf.c Randy Dunlap
2020-05-29 5:24 ` Valdis Klētnieks
2020-05-29 14:02 ` Paul E. McKenney
2020-05-29 13:55 ` Paul E. McKenney
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=538911.1590725791@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.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 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.