search for: finput

Displaying 4 results from an estimated 4 matches for "finput".

Did you mean: input
2020 Jun 16
2
RFC: Adding support for the z/OS platform to LLVM and clang
..., when loading a file, make a determination as to whether a conversion is needed (e.g., consider file tags, environment variables, command line options, etc...) and, if needed, transcode the file contents and register the resulting buffer as an override. This would be useful for implementation of -finput-charset and would benefit deployments in Microsoft environments that have source files in ISO-8859 encodings. Tom.
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...owledge. - UTF8 would be useless on win32. Win32 does not manipulate utf8 implicitly in anywhere. - Path API should hold pathstring as API-native form (bytestream on unix, UCS2 wchar_t on win32). - Path should be manipulated as API-native form as possible. In future, we might consider "-finput-charset" and "-fexec-charset" on clang. Please consider an source file; //////// #include "むすめは/まおちゃん.h" char const literal[] = "俺です、俺俺"; //////// The include path (#include) should be handled as host-dependent. The literal should be interperted with input-chars...
2018 Feb 05
0
LLVM Weekly - #214, Feb 5th 2018
...g 'debuggability' of optimized code. * George Karpenkov wrote up [short investigation of exploration strategies and paths for Clang analyzer](http://lists.llvm.org/pipermail/cfe-dev/2018-January/056718.html). * Sean Perry has been looking at implementing support for `-fexec-charset` and `-finput-charset`, and is [seeking feedback](http://lists.llvm.org/pipermail/cfe-dev/2018-January/056721.html). ## LLVM commits * LLVM's policies on library layering and header isolation have been documented in the coding standards doc. [r324004](http://reviews.llvm.org/rL324004). * The sigil for ma...
2011 Sep 01
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...rward to use utf-8 internally and use the conversion functions provided by the win32 API when calling other win32 API functions, and always call the wide versions of the win32 functions. Full compatibility guaranteed, and one encoding internally. Ruben > > In future, we might consider "-finput-charset" and "-fexec-charset" on clang. > Please consider an source file; > > //////// > #include "むすめは/まおちゃん.h" > char const literal[] = "俺です、俺俺"; > //////// > > The include path (#include) should be handled as host-dependent. The > lit...