From: Mike Stump <mikestump@comcast.net>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: RFA: speeding up dg-extract-results.sh
Date: Thu, 12 Jun 2014 16:32:00 -0000 [thread overview]
Message-ID: <A1BED6CA-DC7F-423C-A361-2235248BD3DF@comcast.net> (raw)
In-Reply-To: <5399CD05.1040406@codesourcery.com>
On Jun 12, 2014, at 8:53 AM, Bernd Schmidt <bernds@codesourcery.com> wrote:
> I've recently been trying to add ada to my set of tested languages, and I now encounter the following:
>
> File "../../git/gcc/../contrib/dg-extract-results.py", line 242, in parse_run
> line = file.readline()
> File "/usr/lib64/python3.3/codecs.py", line 301, in decode
> (result, consumed) = self._buffer_decode(data, self.errors, final)
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 5227: invalid continuation byte
In the old skool world, these are byte sequences that end in ‘\n’… no decoding errors are possible… well, maybe one, if you tried to put ‘\0’ in the stream. :-( Maybe a LANG/LC type person can suggest an environment variable to set that would make things happier, else we’re down to a python person to solve from that side. My knee jerk would be LANG=c for the entire test suite run...
next prev parent reply other threads:[~2014-06-12 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 9:18 Richard Sandiford
2014-05-03 7:34 ` Ping: " Richard Sandiford
2014-05-05 19:17 ` Jakub Jelinek
2014-05-05 20:36 ` Richard Sandiford
2014-05-03 20:07 ` Mike Stump
2014-05-05 16:08 ` Jeff Law
2014-05-05 18:15 ` Mike Stump
2014-05-05 18:16 ` Jeff Law
[not found] ` <CADnVucCA0ozSz=x3z8vexBOkWRj3pquKVuWsFq4xZre0CfxFyQ@mail.gmail.com>
2014-05-19 18:07 ` Richard Sandiford
2014-05-19 18:49 ` Charles Baylis
2014-05-20 10:09 ` Richard Sandiford
2014-05-24 11:17 ` Bernd Schmidt
2014-05-24 17:15 ` Mike Stump
2014-05-24 17:53 ` Trevor Saunders
2014-05-25 9:35 ` Richard Sandiford
2014-06-12 15:53 ` Bernd Schmidt
2014-06-12 16:32 ` Mike Stump [this message]
2014-06-14 9:50 ` Richard Sandiford
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=A1BED6CA-DC7F-423C-A361-2235248BD3DF@comcast.net \
--to=mikestump@comcast.net \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).