On Fri, Dec 9, 2016 at 11:05 AM, Martin Liška wrote:
> On 12/09/2016 11:00 AM, Richard Biener wrote:
>> On Thu, Dec 8, 2016 at 2:37 PM, Martin Liška wrote:
>>> Hello.
>>>
>>> Following patch changes behavior in pretty_print_string, where all
>>> non-printable
>>> characters are encoded as \x%x.
On 12/09/2016 11:00 AM, Richard Biener wrote:
> On Thu, Dec 8, 2016 at 2:37 PM, Martin Liška wrote:
>> Hello.
>>
>> Following patch changes behavior in pretty_print_string, where all
>> non-printable
>> characters are encoded as \x%x. Currently, when some non-printable
>> characters are directly
On Thu, Dec 8, 2016 at 4:00 PM, Martin Liška wrote:
> There's a patch that adds a new test-case for that.
Ok.
> Martin
On Thu, Dec 8, 2016 at 2:37 PM, Martin Liška wrote:
> Hello.
>
> Following patch changes behavior in pretty_print_string, where all
> non-printable
> characters are encoded as \x%x. Currently, when some non-printable characters
> are directly
> printed to a dump file stream. That makes it compli
There's a patch that adds a new test-case for that.
Martin
>From e8805309edca43153721ce3c79252a4f4a3b2073 Mon Sep 17 00:00:00 2001
From: marxin
Date: Thu, 8 Dec 2016 15:59:28 +0100
Subject: [PATCH] New test
gcc/testsuite/ChangeLog:
2016-12-08 Martin Liska
* gcc.dg/tree-ssa/dump-3.c: New te
Hello.
Following patch changes behavior in pretty_print_string, where all non-printable
characters are encoded as \x%x. Currently, when some non-printable characters
are directly
printed to a dump file stream. That makes it complicated to read a dump file
for instance
via a Python script.
Patch