Re: [PATCH] Handle wide-chars in native_encode_string

2017-09-05 Thread Joseph Myers
On Tue, 5 Sep 2017, Richard Biener wrote: > don't have any BITS_PER_UNIT != 8 port (we had c4x). I'm not > sure what constraints we have on CHAR_TYPE_SIZE vs. BITS_PER_UNIT, > or for what port it would make sense to have differing values. BITS_PER_UNIT = size of QImode = unit that target hardwar

Re: [PATCH] Handle wide-chars in native_encode_string

2017-09-05 Thread Richard Biener
On Mon, 4 Sep 2017, Joseph Myers wrote: > On Mon, 4 Sep 2017, Richard Biener wrote: > > > always have a consistend "character" size and how the individual > > "characters" are encoded. The patch assumes that the array element > > type of the STRING_CST can be used to get access to individual > >

Re: [PATCH] Handle wide-chars in native_encode_string

2017-09-04 Thread Joseph Myers
On Mon, 4 Sep 2017, Richard Biener wrote: > always have a consistend "character" size and how the individual > "characters" are encoded. The patch assumes that the array element > type of the STRING_CST can be used to get access to individual > characters by means of the element type size and tho