qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Gwenole Beauchesne <gbeauchesne@mandriva.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: strange crash on FreeBSD-current/amd64 (pointertruncation?)
Date: Fri, 9 Feb 2007 17:31:29 -0500	[thread overview]
Message-ID: <200702091731.29849.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0702090749110.2883@gauss.mandriva.com>

On Friday 09 February 2007 2:06 am, Gwenole Beauchesne wrote:
> In particular, and likely not limited to, a reasonnable C++ ABI

I don't do C++, but Garrett the uClibc++ maintainer used to be at the desk 
next to mine.  He would find this statment hilarious.

Among other things, any _sane_ C++ ABI will deal with nested classes and 
namespaces by listing the innermost one first, so that when you have:

parent1.parent2.parent3.child.member
parent1.parent2.parent3.child.walrus
parent1.parent2.parent3.child.thingy

You don't strcmp your way through 80 bytes of guaranteed-to-be-identical data 
every time you want to do linking or RTTI or anything that needs to find a 
symbol.  This is just one random example of how the people who were doing 
this weren't THINKING.

I'll stop now.

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery

      reply	other threads:[~2007-02-09 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 12:25 [Qemu-devel] Re: strange crash on FreeBSD-current/amd64 (pointertruncation?) Paul Robinson
2007-02-02 17:34 ` Gwenole Beauchesne
2007-02-02 19:03   ` Gwenole Beauchesne
2007-02-08 13:09     ` Rob Landley
2007-02-08 16:09       ` Paul Brook
2007-02-09  7:06       ` Gwenole Beauchesne
2007-02-09 22:31         ` Rob Landley [this message]

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=200702091731.29849.rob@landley.net \
    --to=rob@landley.net \
    --cc=gbeauchesne@mandriva.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).