Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: julian@codesourcery.com
Cc: gdb-patches@sourceware.org, dan@codesourcery.com,
	julian@codesourcery.com
Subject: Re: [PATCH] Interpret DW_TAG_unspecified_type as void
Date: Sun, 18 Jun 2006 01:16:00 -0000	[thread overview]
Message-ID: <200606180114.k5I1E5nu017691@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <448969B2.9010202@codesourcery.com> (message from Julian Brown on 	Fri, 09 Jun 2006 13:29:38 +0100)

> Date: Fri, 09 Jun 2006 13:29:38 +0100
> From: Julian Brown <julian@codesourcery.com>
> 
> Hi,
> 
> This is part of a series of patches from a CodeSourcery branch which 
> enable the output of ARM's RVCT 2.2 compiler to be debugged with gdb.
> 
> This patch handles the C/C++ interpretation of the DWARF 3 construct 
> DW_TAG_unspecified_type as void. This is used in representing e.g. 
> pointer-to-void types. Other languages will currently be handled in 
> exactly the same way; though I'm not entirely sure if that's a sensible 
> default, I don't know what would be better. (Re: section 5.2 of the 
> DWARF 3 doc.)
> 
> Tested natively on x86_64-unknown-linux-gnu and cross to arm-none-eabi 
> with no change in results. Tests against the ARM compiler are improved 
> somewhat.
> 
> OK to apply?

I haven't looked into what the DWARF spec actually says, but
traditionally unspecified types in C default to 'int', not 'void'.


  parent reply	other threads:[~2006-06-18  1:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 12:32 Julian Brown
2006-06-13 23:42 ` Jim Blandy
2006-06-13 23:47   ` Daniel Jacobowitz
2006-06-18  1:16 ` Mark Kettenis [this message]
2006-06-19 12:58   ` Richard Earnshaw

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=200606180114.k5I1E5nu017691@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=julian@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