From: Mark Wielaard <mark@klomp.org>
To: Mao Han <han_mao@c-sky.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [[RESEND & PING]PATCH V3 0/1] Add C-SKY support
Date: Thu, 11 Jul 2019 13:36:00 -0000 [thread overview]
Message-ID: <9ac80d83eedfd1b4da9c5e876919982599a43e68.camel@klomp.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2019-07-11 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 8:17 Mao Han
2019-06-03 8:19 ` [[RESEND & PING]PATCH V3 1/1] Add backend support for C-SKY Mao Han
2019-07-10 22:11 ` Mark Wielaard
2019-07-11 3:20 ` Mao Han
2019-07-14 21:03 ` Mark Wielaard
2019-07-12 22:10 ` Mark Wielaard
2019-07-10 21:33 ` [[RESEND & PING]PATCH V3 0/1] Add C-SKY support Mark Wielaard
2019-07-11 3:13 ` Mao Han
2019-07-11 13:36 ` Mark Wielaard [this message]
2019-07-12 11:24 ` Mao Han
2019-07-12 21:20 ` Mark Wielaard
2019-07-12 21:49 ` Mark Wielaard
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=9ac80d83eedfd1b4da9c5e876919982599a43e68.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=han_mao@c-sky.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).