Date: Wed, 3 Jun 2015 17:23:06 +0200
Message-Id: <201506031523.t53FN6pF006352@ignucius.se.axis.com>
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
In-reply-to: <20150603150426.GF26605@axis.com> (message from Jesper Nilsson on
	Wed, 3 Jun 2015 17:04:26 +0200)
Subject: Re: [PATCH] cris: Wire up missing syscalls
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1312
Lines: 30

> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/