From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: jespern@axis.com
Cc: xili_gchen_5257@hotmail.com, linux-kernel@vger.kernel.org,
linux-cris-kernel@axis.com
Subject: Re: [PATCH] cris: Wire up missing syscalls
Date: Wed, 3 Jun 2015 17:23:06 +0200 [thread overview]
Message-ID: <201506031523.t53FN6pF006352@ignucius.se.axis.com> (raw)
In-Reply-To: <20150603150426.GF26605@axis.com> (message from Jesper Nilsson on Wed, 3 Jun 2015 17:04:26 +0200)
> From: Jesper Nilsson <jespern@axis.com>
> Date: Wed, 3 Jun 2015 17:04:26 +0200
> On Wed, Jun 03, 2015 at 01:36:47PM +0200, Chen Gang wrote:
> > - For v10, need we also use "sys*" instead of "_sys*"?
>
> No, the trick here is that v10 and v32 uses different standards
> with regards to prefixing underscore. I'm hoping to fix that someday.
Not exactly, but almost; please let me fill in JFTR:
Most people probably guessed correctly that this is related to
building the CRIS v10 kernel with the *-elf toolchain (which has
the convention that symbols are prefixed with underscores for
cris-*-elf and crisv32-*-elf) while (IIUC) the CRIS v32 kernel
is built with the *-linux-gnu toolchain (which does not have any
symbol prefix for cris-*-linux-gnu crisv32-*-linux-gnu).
One Might Imagine that there'd be build machinery in place in
the kernel such that such a symbol prefix issue could be hidden,
like a header to include and using e.g. S(symbol) in all
assembly files. (Actually some time ago I thought there already
was, but Jesper corrected me.)
brgds, H-P
next prev parent reply other threads:[~2015-06-03 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 13:48 Chen Gang
2015-06-03 10:20 ` Jesper Nilsson
2015-06-03 11:36 ` Chen Gang
2015-06-03 15:04 ` Jesper Nilsson
2015-06-03 15:23 ` Hans-Peter Nilsson [this message]
2015-06-06 0:15 ` Chen Gang
2015-06-06 0:16 ` Chen Gang
2015-06-04 7:20 ` Jesper Nilsson
2015-06-04 12:46 ` Chen Gang
2015-06-04 12:48 ` Chen Gang
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=201506031523.t53FN6pF006352@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xili_gchen_5257@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome