llvm-project.git/llvm/lib/Support/ConvertUTF.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [Support] Simplify macro conditions involving __GNUC__ (NFC) (#155070) 2025-08-23T14:10:02+00:00 Kazu Hirata kazu@google.com 2025-08-23T14:10:02+00:00 cb1142053fd1136829d635d85d88b2bcf9568432 We require GCC 7.4 these days, so we just need to check for defined(__GNUC__). 
We require GCC 7.4 these days, so we just need to check for
defined(__GNUC__).
 Update license on Unicode.org's ConvertUTF code. 2022-08-12T16:51:08+00:00 James Y Knight jyknight@google.com 2022-08-12T16:36:43+00:00 20451cb06b01167ff4614862736ca65bbfe46dfc The code was relicensed by its owner (Unicode.org) a long time back, but we still had the old (problematic) license in our fork. Note that the source files have not been distributed from unicode.org since 2009 (due to being buggy and unmaintained upstream), but they were given this license before that. Fixes https://github.com/llvm/llvm-project/issues/32309 Differential Revision: https://reviews.llvm.org/D66390 
The code was relicensed by its owner (Unicode.org) a long time back,
but we still had the old (problematic) license in our fork.

Note that the source files have not been distributed from unicode.org
since 2009 (due to being buggy and unmaintained upstream), but they
were given this license before that.

Fixes https://github.com/llvm/llvm-project/issues/32309

Differential Revision: https://reviews.llvm.org/D66390
[Clang] Add a warning on invalid UTF-8 in comments. 2022-07-13T08:19:26+00:00 Corentin Jabot corentinjabot@gmail.com 2022-06-17T14:23:41+00:00 d4892a168f51dabdba255af3a8d23049fcb66960 Introduce an off-by default `-Winvalid-utf8` warning that detects invalid UTF-8 code units sequences in comments. Invalid UTF-8 in other places is already diagnosed, as that cannot appear in identifiers and other grammar constructs. The warning is off by default as its likely to be somewhat disruptive otherwise. This warning allows clang to conform to the yet-to be approved WG21 "P2295R5 Support for UTF-8 as a portable source file encoding" paper. Reviewed By: aaron.ballman, #clang-language-wg Differential Revision: https://reviews.llvm.org/D128059 
Introduce an off-by default `-Winvalid-utf8` warning
that detects invalid UTF-8 code units sequences in comments.

Invalid UTF-8 in other places is already diagnosed,
as that cannot appear in identifiers and other grammar constructs.

The warning is off by default as its likely to be somewhat disruptive
otherwise.

This warning allows clang to conform to the yet-to be approved WG21
"P2295R5 Support for UTF-8 as a portable source file encoding"
paper.

Reviewed By: aaron.ballman, #clang-language-wg

Differential Revision: https://reviews.llvm.org/D128059
Revert "[Clang] Add a warning on invalid UTF-8 in comments." 2022-07-12T22:22:29+00:00 Jonas Devlieghere jonas@devlieghere.com 2022-07-12T22:16:14+00:00 a262f4dbd78fc68609d230f3e9c5ca2b1d1d9437 This reverts commit cc309721d20c8e544ae7a10a66735ccf4981a11c because it breaks the following tests on GreenDragon: TestDataFormatterObjCCF.py TestDataFormatterObjCExpr.py TestDataFormatterObjCKVO.py TestDataFormatterObjCNSBundle.py TestDataFormatterObjCNSData.py TestDataFormatterObjCNSError.py TestDataFormatterObjCNSNumber.py TestDataFormatterObjCNSURL.py TestDataFormatterObjCPlain.py TestDataFormatterObjNSException.py https://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/45288/ 
This reverts commit cc309721d20c8e544ae7a10a66735ccf4981a11c because it
breaks the following tests on GreenDragon:

  TestDataFormatterObjCCF.py
  TestDataFormatterObjCExpr.py
  TestDataFormatterObjCKVO.py
  TestDataFormatterObjCNSBundle.py
  TestDataFormatterObjCNSData.py
  TestDataFormatterObjCNSError.py
  TestDataFormatterObjCNSNumber.py
  TestDataFormatterObjCNSURL.py
  TestDataFormatterObjCPlain.py
  TestDataFormatterObjNSException.py

https://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/45288/
[Clang] Add a warning on invalid UTF-8 in comments. 2022-07-12T12:34:30+00:00 Corentin Jabot corentinjabot@gmail.com 2022-06-17T14:23:41+00:00 cc309721d20c8e544ae7a10a66735ccf4981a11c Introduce an off-by default `-Winvalid-utf8` warning that detects invalid UTF-8 code units sequences in comments. Invalid UTF-8 in other places is already diagnosed, as that cannot appear in identifiers and other grammar constructs. The warning is off by default as its likely to be somewhat disruptive otherwise. This warning allows clang to conform to the yet-to be approved WG21 "P2295R5 Support for UTF-8 as a portable source file encoding" paper. Reviewed By: aaron.ballman, #clang-language-wg Differential Revision: https://reviews.llvm.org/D128059 
Introduce an off-by default `-Winvalid-utf8` warning
that detects invalid UTF-8 code units sequences in comments.

Invalid UTF-8 in other places is already diagnosed,
as that cannot appear in identifiers and other grammar constructs.

The warning is off by default as its likely to be somewhat disruptive
otherwise.

This warning allows clang to conform to the yet-to be approved WG21
"P2295R5 Support for UTF-8 as a portable source file encoding"
paper.

Reviewed By: aaron.ballman, #clang-language-wg

Differential Revision: https://reviews.llvm.org/D128059
Revert "[Clang] Add a warning on invalid UTF-8 in comments." 2022-07-09T15:18:35+00:00 Corentin Jabot corentinjabot@gmail.com 2022-07-09T15:18:35+00:00 50416e5454d802a3ef71bb799e5bfd38e8ec9089 It is probable thart this change crashes on the powerpc bots. This reverts commit 355532a1499aa9b13a89fb5b5caaba2344d57cd7. 
It is probable thart this change crashes on the powerpc bots.

This reverts commit 355532a1499aa9b13a89fb5b5caaba2344d57cd7.
[Clang] Add a warning on invalid UTF-8 in comments. 2022-07-09T09:26:45+00:00 Corentin Jabot corentinjabot@gmail.com 2022-06-17T14:23:41+00:00 355532a1499aa9b13a89fb5b5caaba2344d57cd7 Introduce an off-by default `-Winvalid-utf8` warning that detects invalid UTF-8 code units sequences in comments. Invalid UTF-8 in other places is already diagnosed, as that cannot appear in identifiers and other grammar constructs. The warning is off by default as its likely to be somewhat disruptive otherwise. This warning allows clang to conform to the yet-to be approved WG21 "P2295R5 Support for UTF-8 as a portable source file encoding" paper. Reviewed By: aaron.ballman, #clang-language-wg Differential Revision: https://reviews.llvm.org/D128059 
Introduce an off-by default `-Winvalid-utf8` warning
that detects invalid UTF-8 code units sequences in comments.

Invalid UTF-8 in other places is already diagnosed,
as that cannot appear in identifiers and other grammar constructs.

The warning is off by default as its likely to be somewhat disruptive
otherwise.

This warning allows clang to conform to the yet-to be approved WG21
"P2295R5 Support for UTF-8 as a portable source file encoding"
paper.

Reviewed By: aaron.ballman, #clang-language-wg

Differential Revision: https://reviews.llvm.org/D128059
Revert "[Clang] Add a warning on invalid UTF-8 in comments." 2022-07-06T20:51:52+00:00 Nico Weber thakis@chromium.org 2022-07-06T20:51:42+00:00 e9fe20dab39edb911afacdb6ed9ec2c7499a59cf This reverts commit 4174f0ca618b467571b43cff12cbe4c4239670f8. Also revert follow-up "[Clang] Fix invalid utf-8 detection" This reverts commit bf45e27a676d87944f1f13d5f0d0f39935fc4010. The second commit broke tests, see comments on https://reviews.llvm.org/D129223, and it sounds like the first commit isn't valid without the second one. So reverting both for now. 
This reverts commit 4174f0ca618b467571b43cff12cbe4c4239670f8.

Also revert follow-up "[Clang] Fix invalid utf-8 detection"
This reverts commit bf45e27a676d87944f1f13d5f0d0f39935fc4010.

The second commit broke tests, see comments on
https://reviews.llvm.org/D129223, and it sounds like the first
commit isn't valid without the second one. So reverting both for now.
[Clang] Fix invalid utf-8 detection 2022-07-06T20:20:04+00:00 Corentin Jabot corentinjabot@gmail.com 2022-07-06T20:16:22+00:00 bf45e27a676d87944f1f13d5f0d0f39935fc4010 The length of valid codepoints was incorrectly calculated which was not caught before because the absence of tests for the valid codepoints scenario. Differential Revision: https://reviews.llvm.org/D129223 
The length of valid codepoints was incorrectly
calculated which was not caught before because the
absence of tests for the valid codepoints scenario.

Differential Revision: https://reviews.llvm.org/D129223
[Clang] Add a warning on invalid UTF-8 in comments. 2022-07-06T19:18:29+00:00 Corentin Jabot corentinjabot@gmail.com 2022-06-17T14:23:41+00:00 4174f0ca618b467571b43cff12cbe4c4239670f8 Introduce an off-by default `-Winvalid-utf8` warning that detects invalid UTF-8 code units sequences in comments. Invalid UTF-8 in other places is already diagnosed, as that cannot appear in identifiers and other grammar constructs. The warning is off by default as its likely to be somewhat disruptive otherwise. This warning allows clang to conform to the yet-to be approved WG21 "P2295R5 Support for UTF-8 as a portable source file encoding" paper. Reviewed By: aaron.ballman, #clang-language-wg Differential Revision: https://reviews.llvm.org/D128059 
Introduce an off-by default `-Winvalid-utf8` warning
that detects invalid UTF-8 code units sequences in comments.

Invalid UTF-8 in other places is already diagnosed,
as that cannot appear in identifiers and other grammar constructs.

The warning is off by default as its likely to be somewhat disruptive
otherwise.

This warning allows clang to conform to the yet-to be approved WG21
"P2295R5 Support for UTF-8 as a portable source file encoding"
paper.

Reviewed By: aaron.ballman, #clang-language-wg

Differential Revision: https://reviews.llvm.org/D128059