Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Mark Kettenis <kettenis@chello.nl>,
	jh@suse.cz, aj@suse.de, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Classify non-POD struct types more or less correctly on AMD64
Date: Wed, 10 Mar 2004 04:21:00 -0000	[thread overview]
Message-ID: <20040310042105.GA18320@nevyn.them.org> (raw)
In-Reply-To: <404E8DB7.1070406@codesourcery.com>

On Tue, Mar 09, 2004 at 07:38:31PM -0800, Mark Mitchell wrote:
> Daniel Jacobowitz wrote:
> 
> >I don't know if this sort of information should be in the dwarf2
> >information somehow.  It definitely is in the C++ GNU v3 ABI:
> >  http://www.codesourcery.com/cxx-abi/abi.html#calls
> 
> I think it should definitely be encoded in DWARF2.  (I don't know where; 
> I just think it's a mistake for the debugger to be trying to figure this 
> out for itself.  The rules are pretty subtle, and may be different from 
> architecture to architecture, or compiler release to compiler release, 
> even, if we make an intentional change.)
> 
> For stabs, you're probably hosed -- but then again, aren't you just 
> generally hosed with stabs? :-)

Amen.

> >I'm guessing that this is what the x86-64 ABI was referring to, rather
> >than the actual term POD.
> 
> Yes.

OK, thanks.  I don't believe there is an appropriate existing tag for
this, so if we get sufficiently fed up with trying to guess, we'll have
to propose one :)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Mark Kettenis <kettenis@chello.nl>,
	jh@suse.cz, aj@suse.de, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Classify non-POD struct types more or less correctly on AMD64
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <20040310042105.GA18320@nevyn.them.org> (raw)
Message-ID: <20040319000900.mxVrW1AT8wNlTABGb2DN3sFdEBV92o1oL4yM5BuRNHk@z> (raw)
In-Reply-To: <404E8DB7.1070406@codesourcery.com>

On Tue, Mar 09, 2004 at 07:38:31PM -0800, Mark Mitchell wrote:
> Daniel Jacobowitz wrote:
> 
> >I don't know if this sort of information should be in the dwarf2
> >information somehow.  It definitely is in the C++ GNU v3 ABI:
> >  http://www.codesourcery.com/cxx-abi/abi.html#calls
> 
> I think it should definitely be encoded in DWARF2.  (I don't know where; 
> I just think it's a mistake for the debugger to be trying to figure this 
> out for itself.  The rules are pretty subtle, and may be different from 
> architecture to architecture, or compiler release to compiler release, 
> even, if we make an intentional change.)
> 
> For stabs, you're probably hosed -- but then again, aren't you just 
> generally hosed with stabs? :-)

Amen.

> >I'm guessing that this is what the x86-64 ABI was referring to, rather
> >than the actual term POD.
> 
> Yes.

OK, thanks.  I don't believe there is an appropriate existing tag for
this, so if we get sufficiently fed up with trying to guess, we'll have
to propose one :)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2004-03-10  4:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 18:00 Mark Kettenis
2004-01-10 18:36 ` Daniel Jacobowitz
2004-01-10 18:59   ` Mark Kettenis
2004-01-11  4:10     ` Daniel Jacobowitz
2004-01-11 12:38       ` Mark Kettenis
2004-01-11 13:29         ` Jan Hubicka
2004-01-12  5:37           ` Mark Mitchell
2004-01-11 15:05         ` Gabriel Dos Reis
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-09 15:39           ` Daniel Jacobowitz
2004-03-19  0:09           ` Mark Mitchell
2004-03-10  3:38             ` Mark Mitchell
2004-03-10  4:21             ` Daniel Jacobowitz [this message]
2004-03-19  0:09               ` Daniel Jacobowitz

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=20040310042105.GA18320@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=aj@suse.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jh@suse.cz \
    --cc=kettenis@chello.nl \
    --cc=mark@codesourcery.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