diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2021-07-06 07:04:19 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-06 07:04:19 +0000 |
| commit | 630efc56d1059bac464b38807dab58cd322f7a7f (patch) | |
| tree | 6e3a1c42920a2dd59c1509c92dba376e51a1ffa4 /gcc/gcov-io.h | |
| parent | 27b3d34428801397e562b7fcc5ca10b13961f3e1 (diff) | |
| parent | 94ada647bf35c727c17ade60d06af6803a7e5668 (diff) | |
| download | gcc-630efc56d1059bac464b38807dab58cd322f7a7f.zip gcc-630efc56d1059bac464b38807dab58cd322f7a7f.tar.gz gcc-630efc56d1059bac464b38807dab58cd322f7a7f.tar.bz2 | |
Merge #552
552: UTF-8 BOM handling r=dkm a=dkm
Mark Wielaard (https://gcc.gnu.org/pipermail/gcc-rust/2021-July/000072.html ) :
> A rust source file can start with a UTF-8 BOM sequence (EF BB
> BF). This simply indicates that the file is encoded as UTF-8 (all rust
> input is interpreted as asequence of Unicode code points encoded in
> UTF-8) so can be skipped before starting real lexing.
>
> It isn't necessary to keep track of the BOM in the AST or HIR Crate
> classes. So I removed the has_utf8bom flag.
>
> Also included are a couple of simple tests to show we handle the BOM
> correctly now.
Co-authored-by: Mark Wielaard <mark@klomp.org>
Diffstat (limited to 'gcc/gcov-io.h')
0 files changed, 0 insertions, 0 deletions