This is the mail archive of the
elfutils-devel@sourceware.org
mailing list for the elfutils project.
Re: [[RESEND & PING]PATCH V3 0/1] Add C-SKY support
- From: Mark Wielaard <mark at klomp dot org>
- To: Mao Han <han_mao at c-sky dot com>
- Cc: elfutils-devel at sourceware dot org
- Date: Thu, 11 Jul 2019 15:36:03 +0200
- Subject: Re: [[RESEND & PING]PATCH V3 0/1] Add C-SKY support
- References: <cover.1559544994.git.han_mao@c-sky.com> <1539116e9ac2bfb0871481291ea0081287544e0f.camel@klomp.org> <20190711031142.GA824@vmh-VirtualBox>
On Thu, 2019-07-11 at 11:11 +0800, Mao Han wrote:
> On Wed, Jul 10, 2019 at 11:33:23PM +0200, Mark Wielaard wrote:
> > On Mon, 2019-06-03 at 16:16 +0800, Mao Han wrote:
> > > test binary:
> > > https://github.com/c-sky/test-result/blob/master/elfutils/divzero
> > > https://github.com/c-sky/test-result/blob/master/elfutils/core
> >
> > I was looking at these, but they seem to have a wrong e_machine
> > value
> > of EM_RCE, not EM_CSKY? Is that deliberate?
> >
>
> I used an no upstream toolchain to verify coredump backtrace, which
> use
> the EM_CSKY_OLD equals to 39. We have changed the EM number to 252 in
> our newly released toolchain with compatibility to EM_CSKY_OLD.
> See binutils/include/elf/common.h:
> /* C-SKY historically used 39, the same value as MCORE, from which
> the
> architecture was derived. */
> #define EM_CSKY_OLD EM_MCORE
Aha. But that is unfortunate on 2 levels. First EM_MCORE isn't an
official e_machine name. The value 39 is associated with EM_RCE for the
Morotola RCE. I assume those are the same thing?
Second, it makes it hard to check the elfutils backend since you'll
have to comment out all EM_RCE usage, and change the EM_CSKY to the old
value.
Do you have any binaries/core files generated by an upstream toolchain
that uses the assigned ELF values? That would be really helpful running
some tests.
Thanks,
Mark