-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[libc++] Re-enable the clang_modules_include test for Objective-C++ #66801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@llvm/pr-subscribers-libcxx @llvm/pr-subscribers-clang ChangesThis reverts commit aa60b26, which was a temporary workaround. This was originally https://reviews.llvm.org/D158694. Full diff: https://github.com/llvm/llvm-project/pull/66801.diff 2 Files Affected:
diff --git a/clang/foo b/clang/foo
new file mode 100644
index 000000000000000..e69de29bb2d1d64
diff --git a/libcxx/test/libcxx/clang_modules_include.gen.py b/libcxx/test/libcxx/clang_modules_include.gen.py
index b4c5c79a47f6823..b4aecfe5d8faae6 100644
--- a/libcxx/test/libcxx/clang_modules_include.gen.py
+++ b/libcxx/test/libcxx/clang_modules_include.gen.py
@@ -44,11 +44,8 @@
#include <{header}>
""")
-# TODO: Remove the UNSUPPORTED{BLOCKLIT}: clang-modules-build once issues with this test have been figured out.
print(f"""\
//--- __std_clang_module.compile.pass.mm
-// UNSUPPORTED{BLOCKLIT}: clang-modules-build
-
// RUN{BLOCKLIT}: %{{cxx}} %s %{{flags}} %{{compile_flags}} -fmodules -fcxx-modules -fmodules-cache-path=%t -fsyntax-only
// REQUIRES{BLOCKLIT}: clang-modules-build
|
@mordante I'm not certain what's going on here, I get
Can you assist? It only happens with Clang trunk. |
I tested this locally and indeed it works with clang-17 and fails with clang-18 @ChuanqiXu9 This seems to be introduced in 574ee1c. This test uses a Objective-C++ file. Is it easy for you to fix or should I file a bug report? |
The motivation of my change was that I find multiple people are trying to fake |
I tried to fix this in c2c840b. Sorry for disturbing. |
Thanks for the quick fix! I've tested the fix with this patch locally and it passes. |
7683064
to
f056692
Compare
Thanks folks! I rebased and I'm re-running the CI. I'll merge once it's green. |
You can test this locally with the following command:darker --check --diff -r 1ec5b1f483aa154255d919af9abf5eca2fe8635c...217e8477c88eb994ae5beb14dcac9162385e1289 libcxx/test/libcxx/clang_modules_include.gen.py View the diff from darker here.--- clang_modules_include.gen.py 2024-03-11 13:54:19.000000 +0000
+++ clang_modules_include.gen.py 2024-03-11 13:57:33.782661 +0000
@@ -45,11 +45,12 @@
{lit_header_restrictions.get(header, '')}
#include <{header}>
""")
-print(f"""\
+print(
+ f"""\
//--- __std_clang_module.compile.pass.mm
// RUN{BLOCKLIT}: %{{cxx}} %s %{{flags}} %{{compile_flags}} -fmodules -fcxx-modules -fmodules-cache-path=%t -fsyntax-only
// REQUIRES{BLOCKLIT}: clang-modules-build
@@ -69,6 +70,7 @@
// TODO: Investigate this failure
// UNSUPPORTED{BLOCKLIT}: LIBCXX-FREEBSD-FIXME
@import std;
-""")
+"""
+)
|
bb67a57
to
e638ee5
Compare
I rebased again. Last time I rebased there was still the same Clang issue. |
I guess nobody ever updated our Docker image. I want to look at that soon so we can start testing LLVM-19 in the CI. |
e638ee5
to
b5ee867
Compare
This reverts commit aa60b26, which was a temporary workaround.
b5ee867
to
217e847
Compare
Merging since the relevant tests have passed. |
This reverts commit aa60b26, which was a temporary workaround.
The underlying issue was fixed in Clang via c2c840b.
This was originally https://reviews.llvm.org/D158694.