From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Chris Metcalf <cmetcalf@ezchip.com>,
riku.voipio@iki.fi, Peter Maydell <peter.maydell@linaro.org>
Cc: "walt@tilera.com" <walt@tilera.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tile: Can load elf64 tilegx binary successfully for linux-user.
Date: Fri, 13 Feb 2015 12:03:16 +0800 [thread overview]
Message-ID: <54DD7784.80504@sunrus.com.cn> (raw)
In-Reply-To: <54DD2A18.1030500@ezchip.com>
On 2/13/15 06:32, Chris Metcalf wrote:
> On 2/11/2015 10:48 PM, Chen Gang S wrote:
>> On 2/12/15 11:32, Chen Gang S wrote:
>>>>>>> >>> >> +#define EM_TILE 191 /* Tile */
>>>>>>> >>> >>+#define EM_TILE_OLD 0x2597 /* Tile compat */
>>>>> >> >
>>>>> >> >No need for EM_TILE_OLD - it never really got out into the wild.
>>>>> >> >
>>>>> >> >Also, 191 is EM_TILEGX in <elf.h>, so you really should use the same name here, not EM_TILE.
>>>>> >> >
>> Oh, I can not fine EM_TILEGX in "elf.h" in master branch. I guess, I
>> need to define it, too.
>
> It is in glibc's /usr/include/elf.h since version 2.16.
>
OK, thanks. Really it is, and glibc also defines another archs (e.g.
microblaze). But I guess, at present, we have to use qemu's "elf.h":
- qemu may use another libc libraries (e.g. newlibc, I guess), which
may not have these macros.
- If qemu will consider about the system elf.h file in the future, it
will change all related macros (it almost means rewrite its elf.h).
So for me, at present, just follow with the current qemu's elf.h is OK:
(define EM_TILEGX directly without ifdef EM_TILEGX or endif).
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-02-13 3:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 0:00 [Qemu-devel] [PATCH] tile: Can load elf64 tilegx binary successfully for linux-user Chen Gang S
2015-02-12 0:12 ` Chen Gang S
2015-02-12 0:24 ` Chris Metcalf
2015-02-12 3:32 ` Chen Gang S
2015-02-12 3:48 ` Chen Gang S
2015-02-12 22:32 ` Chris Metcalf
2015-02-13 4:03 ` Chen Gang S [this message]
2015-02-12 22:31 ` Chris Metcalf
2015-02-13 4:43 ` Chen Gang S
2015-02-13 4:56 ` Peter Maydell
2015-02-13 5:44 ` Chen Gang S
2015-02-13 5:43 ` Peter Maydell
2015-02-13 6:34 ` Chen Gang S
2015-02-12 0:49 ` Peter Maydell
2015-02-12 2:53 ` Chen Gang S
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=54DD7784.80504@sunrus.com.cn \
--to=gang.chen@sunrus.com.cn \
--cc=cmetcalf@ezchip.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=walt@tilera.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 NNTP newsgroup(s).