Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Cleaner handling of character entities ?
Date: Fri, 05 May 2006 18:29:00 -0000	[thread overview]
Message-ID: <20060505182852.GL31029@nevyn.them.org> (raw)
In-Reply-To: <20060505182351.GK1109@adacore.com>

On Fri, May 05, 2006 at 11:23:51AM -0700, Joel Brobecker wrote:
> I think the attached patch improves the situation in terms of making
> things cleaner in the case of dwarf2, without impacting targets that
> still use older debugging format like stabs.
> 
> 2006-05-05  Joel Brobecker  <brobecker@adacore.com>
> 
>         * dwarf2read.c (read_base_type): Set code to TYPE_CODE_CHAR
>         for char and unsigned char types.
>         * ada-lang.c (ada_is_character_type): Always return true if
>         the type code is TYPE_CODE_CHAR.
>         * c-valprint.c (c_val_print): Print arrays whose element type
>         code is TYPE_CODE_CHAR as strings.
> 
> Tested on x86-linux, with GCC 3.4 (dwarf2, stabs+), GCC 4.1 (dwarf2).
> No regression.
> 
> What do you guys think? Wouldn't that be a step forward?

I really suspect this impacts the existing producers in some way,
though I don't know exactly how.  You should take a look at the most
recent Modula-2 patch, and the discussion around the previous posting
of it, which contained very similar changes (conditionalized for M2).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-05 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 18:24 Joel Brobecker
2006-05-05 18:29 ` Daniel Jacobowitz [this message]
2006-05-05 19:06   ` Joel Brobecker
2006-05-05 19:40     ` Jim Blandy
2006-05-05 19:48       ` Daniel Jacobowitz
2006-05-05 20:54         ` Joel Brobecker
2006-05-05 21:47         ` Jim Blandy
2006-05-15 19:06           ` Daniel Jacobowitz
2007-12-24  8:00             ` Joel Brobecker

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=20060505182852.GL31029@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.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