This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC] Adjust output for strings in tree-pretty-print.c

From: FX <fxcoudert at gmail dot com>
To: "Paolo Bonzini" <bonzini at gnu dot org>
Cc: "GCC Development" <gcc at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Mon, 19 May 2008 15:59:43 +0100
Subject: Re: [RFC] Adjust output for strings in tree-pretty-print.c
References: <19c433eb0805190659g7442d645ga7755ec598856463@mail.gmail.com> <4831925D.5020302@gnu.org>

> I think the best thing to do is to have a langhook then.

It seems a bit weird to have a langhook for a one-character
difference, but if there's a consensus on it, I'll go along.

> Endianness issues may also appear.  Maybe you should call iconv in the
> langhook to get back to UTF-8, and print that representation instead.

Endianness is already take care of, in the sense that the string is
encoded in the target's endianness already. However, that makes
calling iconv more difficult, because that has us going from target's
endianness to UTF-8, which will be a pain. As only developers do read
tree dumps, I think having a lot of \0 in them is fine.


FX

-- 
FX Coudert
http://www.homepages.ucl.ac.uk/~uccafco/

Follow-Ups:
- Re: [RFC] Adjust output for strings in tree-pretty-print.c
  - From: Paolo Bonzini

References:
- [RFC] Adjust output for strings in tree-pretty-print.c
  - From: FX
- Re: [RFC] Adjust output for strings in tree-pretty-print.c
  - From: Paolo Bonzini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]