-
Notifications
You must be signed in to change notification settings - Fork 3.4k
import the already imported part of llvm-libc from HEAD #24604
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
Lets see if all the tests pass (i.e. lets see if libc++ is effected by this change).
Also, can you remove the llvm-libc stuff from system/lib/update_libcxx.py
system/lib/update_llvm_libc.py
Outdated
script_dir = os.path.abspath(os.path.dirname(__file__)) | ||
emscripten_root = os.path.dirname(os.path.dirname(script_dir)) | ||
default_llvm_dir = os.path.join(os.path.dirname(emscripten_root), 'llvm-project') | ||
emscripten_patches = os.path.join(script_dir, "llvm-libc", "patches", "*.patch") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't tend to check in patches like this, at least not for the other libraries here. Instead we push our changes out to https://github.com/emscripten-core/llvm-project and maintain the patches in git.
I'm not totally opposed to this approach here, but it would be new thing for us.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose those patches are not submitted to the upstream?
If I understand correctly, you want me to submit the content of this patch to emscripten's fork of llvm?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, can you update the readme file in the llvm-libc directory?
Done.
Tests are failing due to some differences in the expected code size. Can you give me a pointer on how those are updated? |
Importing llvm-libc from HEAD instead of llvm-20.
Add some basic file filtering and patch applying logic in the import script
system/lib/update_llvm_libc.py
.Tested:
The same number of tests failing at HEAD when running
./test/runner llvmlibc
.#24493