From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Morton, Derek J" <derek.j.morton@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Wood, Thomas" <thomas.wood@intel.com>,
"Gore, Tim" <tim.gore@intel.com>
Subject: Re: [PATCH i-g-t] tests/gem_exec_nop: Improved test run time
Date: Wed, 4 Nov 2015 15:07:15 +0000 [thread overview]
Message-ID: <563A1F23.5000507@linux.intel.com> (raw)
In-Reply-To: <2D016F5BA44C744783BA96B1D3EBC5BD13EADEFC@IRSMSX102.ger.corp.intel.com>
On 04/11/15 14:46, Morton, Derek J wrote:
>>
>>
>> -----Original Message-----
>> From: Tvrtko Ursulin [mailto:tvrtko.ursulin@linux.intel.com]
>> Sent: Wednesday, November 4, 2015 2:34 PM
>> To: Chris Wilson; Morton, Derek J; intel-gfx@lists.freedesktop.org; Wood, Thomas; Gore, Tim
>> Subject: Re: [Intel-gfx] [PATCH i-g-t] tests/gem_exec_nop: Improved test run time
>>
>>
>> On 04/11/15 14:24, Chris Wilson wrote:
>>> On Wed, Nov 04, 2015 at 02:10:36PM +0000, Morton, Derek J wrote:
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Chris Wilson [mailto:chris@chris-wilson.co.uk] No, just
>>>>> android appears to be broken. I was actually complaining about the use of 'S'.
>>>>
>>>> What would you prefer to be printed?
>>>
>>> Prefer? µs. us if we must.
>>
>> Is this not just about the encoding supported by the terminal of the user running the test? In case of Android it is the adb shell them which does not support UTF-8?
>
> Actually the µs works fine on android if setlocale() is not called. The problem is that when called on android it sets a very basic locale with ascii character set.
>
> I am assuming it was added for a good reason and can't just be removed so the second best option is going to be to use 'us'.
It allows programs to respect some of the locale settings, but should
not cause raw C strings to be modified I would have thought. So to me it
also looks like a bug somewhere in the stack. A bit curious.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-11-04 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 16:29 [PATCH i-g-t] tests/gem_exec_nop: Improved test run time Derek Morton
2015-11-03 16:39 ` Chris Wilson
2015-11-04 13:40 ` Morton, Derek J
2015-11-04 13:55 ` Chris Wilson
2015-11-04 14:10 ` Morton, Derek J
2015-11-04 14:24 ` Chris Wilson
2015-11-04 14:34 ` Tvrtko Ursulin
2015-11-04 14:46 ` Morton, Derek J
2015-11-04 15:07 ` Tvrtko Ursulin [this message]
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=563A1F23.5000507@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=derek.j.morton@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@intel.com \
--cc=tim.gore@intel.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