Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Doug Evans <xdje42@gmail.com>,
	Sandra Loosemore <sandra@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [patch, testsuite] check for UTF-32 target wide charset support in gdb.base/wchar.exp
Date: Tue, 29 Sep 2015 13:50:00 -0000	[thread overview]
Message-ID: <560A9723.3050108@redhat.com> (raw)
In-Reply-To: <m3si6cqqos.fsf@sspiff.org>

On 09/18/2015 05:47 AM, Doug Evans wrote:

> The question I have is what's the intent behind PHONY_ICONV?
> [The fact that it apparently tries to provide some minimal wide char
> support but defines GDB_DEFAULT_TARGET_WIDE_CHARSET as "ISO-8859-1"
> seems like a bug to me.]
> 
> Is it intended that it provide some minimal wide char support?

I recall the feature being submitted and the follow up Solaris fixes,
but I wasn't the one doing the work, so I'm not 100% sure of anything,
but I believe the intention is to punt on wide char support with the least
extra code possible.  That seems to be what the original submission
suggests as well:

 https://sourceware.org/ml/gdb-patches/2009-01/msg00533.html
 https://sourceware.org/ml/gdb-patches/2009-03/msg00420.html

along with the comments in mails around the follow up Solaris fixes:

 https://www.sourceware.org/ml/gdb-patches/2010-08/msg00339.html

Thanks,
Pedro Alves


  reply	other threads:[~2015-09-29 13:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  3:25 Sandra Loosemore
2015-09-17  4:31 ` Doug Evans
2015-09-17  5:10   ` Eli Zaretskii
2015-09-18  4:38     ` Doug Evans
2015-09-17  5:07 ` Eli Zaretskii
2015-09-17  5:17   ` Sandra Loosemore
2015-09-17  5:59     ` Eli Zaretskii
2015-09-18  4:48     ` Doug Evans
2015-09-29 13:50       ` Pedro Alves [this message]
2015-09-18  4:41   ` Doug Evans

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=560A9723.3050108@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sandra@codesourcery.com \
    --cc=xdje42@gmail.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