From: Stuart Anderson <anderson@netsweng.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user target
Date: Wed, 18 Apr 2007 15:30:56 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704181522300.22280@trantor.stuart.netsweng.com> (raw)
In-Reply-To: <1176921819.6333.85.camel@rapid>
On Wed, 18 Apr 2007, J. Mayer wrote:
> You're right: I think all TLS specific code is located in the glibc.
In my last tracing through qemu.log, I did check for r2 references, and
there was one store near the beginning that looked like what glibc would
do (r2 = ptr+0x700), and the rest of the access were reads of r2.
> It may be related to some of the library versions installed in
> your 64 bits environment that would not be the same as the one used in
> the 32 bits environment.
Both are current Debian etch systems, a real x86_64, and a real x86.
Both are running the same library versions.
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
> One important
> precision that may make a big difference: I always use gcc 3.4 to
> compile because I know several gcc 4.x bugs (crash during ISO C
> compliant code and/or incorrect generated asm instructions), then I do
> not consider gcc 4.x as usable for a production environment today.
I'm using gcc-3.4 as well.
ii gcc-3.4 3.4.6-5 The GNU C compiler
ii gcc-3.4-base 3.4.6-5 The GNU Compiler Collection (base package)
Stuart
Stuart R. Anderson anderson@netsweng.com
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
next prev parent reply other threads:[~2007-04-18 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 13:34 [Qemu-devel] (no subject) Stuart Anderson
2007-04-10 18:11 ` [Qemu-devel] linux-user target Jocelyn Mayer
2007-04-10 18:27 ` Stuart Anderson
2007-04-17 20:55 ` Stuart Anderson
2007-04-18 17:31 ` Stuart Anderson
2007-04-18 18:43 ` J. Mayer
2007-04-18 19:30 ` Stuart Anderson [this message]
2007-04-18 19:52 ` Igor Kovalenko
2007-04-18 20:15 ` Stuart Anderson
2007-04-18 20:32 ` Igor Kovalenko
2007-04-18 20:42 ` Stuart Anderson
2007-04-19 8:32 ` J. Mayer
2007-04-19 17:04 ` Stuart Anderson
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=Pine.LNX.4.64.0704181522300.22280@trantor.stuart.netsweng.com \
--to=anderson@netsweng.com \
--cc=qemu-devel@nongnu.org \
/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).