Re: gcc/libcpp: non-UTF-8 source or execution encodings?

On Tue, 2016-07-19 at 16:10 -0700, David Edelsohn wrote: > Hi, David > > I don't believe that hardware easily is available. We probably could > arrange for access, if it is necessary, but it is not accessible > through the IBM Community Development system for Linux on z Systems > because this

Re: gcc/libcpp: non-UTF-8 source or execution encodings?

David Edelsohn writes: > GCC on the system is not self-hosting -- I believe that GCC only is > used as a cross-compiler. I can confirm this - GCC for TPF is always a cross compiler, it never runs *on* a TPF system.

Re: gcc/libcpp: non-UTF-8 source or execution encodings?

Hi, David I don't believe that hardware easily is available. We probably could arrange for access, if it is necessary, but it is not accessible through the IBM Community Development system for Linux on z Systems because this isn't Linux-based. GCC on the system is not self-hosting -- I believe

Re: gcc/libcpp: non-UTF-8 source or execution encodings?

On Tue, 2016-07-19 at 12:24 -0400, David Edelsohn wrote: > On Tue, Jul 19, 2016 at 12:05 PM, David Malcolm > wrote: > > libcpp/charset.c has a helpful introductory comment > > describingcharacter > > sets, including the source and execution character sets. > > > > libcpp

Re: gcc/libcpp: non-UTF-8 source or execution encodings?

On Tue, Jul 19, 2016 at 12:05 PM, David Malcolm wrote: > libcpp/charset.c has a helpful introductory comment describingcharacter > sets, including the source and execution character sets. > > libcpp appears to attempt to support both UTF-8 and UTF-EBCDIC for the > source

gcc/libcpp: non-UTF-8 source or execution encodings?

libcpp/charset.c has a helpful introductory comment describingcharacter sets, including the source and execution character sets. libcpp appears to attempt to support both UTF-8 and UTF-EBCDIC for the source character set, via: #if HOST_CHARSET == HOST_CHARSET_ASCII #define SOURCE_CHARSET "UTF-8"