[llvm-dev] RFC: Adding support for the z/OS platform to LLVM and clang

[Kai Peter Nacke via llvm-dev]

Hubert Tong <hubert.reinterpretcast at gmail.com> wrote on 10.06.2020 
23:51:54:

> From: Hubert Tong <hubert.reinterpretcast at gmail.com>
> To: Kai Peter Nacke <kai.nacke at de.ibm.com>
> Cc: llvm-dev <llvm-dev at lists.llvm.org>
> Date: 10.06.2020 23:52
> Subject: [EXTERNAL] Re: [llvm-dev] RFC: Adding support for the z/OS 
> platform to LLVM and clang
> 
> On Wed, Jun 10, 2020 at 3:11 PM Kai Peter Nacke via llvm-dev <llvm-
> dev at lists.llvm.org> wrote:
> 2) Add patches to Clang to allow EBCDIC and ASCII (ISO-8859-1) encoded 
> input source files. This would be done at the file open time to allow 
the 
> rest of Clang to operate as if the source was UTF-8 and so require no 
> changes downstream. Feedback on this plan is welcome from the Clang 
> community.
> Is there a statement that can be made with respect to accepting 
> UTF-8 encoded source files in a z/OS hosted environment or is it 
> implied that it works with no changes (and there are no changes that
> will break this functionality)?
> 
> Also, would these changes enable the consumption of non-UTF-8 
> encoded source files on Clang as hosted on other platforms?

The intention is to use the auto-conversion feature from the
language environment. Currently, this platform feature does not
handle conversions of multi-byte encodings, so at this time
consumption of UTF-8 encoded source files is not possible.
For the same reason, this does not enable the consumption of
non-UTF-8 encoded source files on other platforms.

Best regards,
Kai Nacke
IT Architect

IBM Deutschland GmbH
Vorsitzender des Aufsichtsrats: Sebastian Krause
Geschäftsführung: Gregor Pillen (Vorsitzender), Agnes Heftberger, Norbert 
Janzen, Markus Koerner, Christian Noll, Nicole Reimer
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, 
HRB 14562 / WEEE-Reg.-Nr. DE 99369940