Details
- Reviewers
sfertile ruiu • espindola - Group Reviewers
Restricted Project
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
Unit tests: pass. 61237 tests passed, 0 failed and 729 were skipped.
clang-tidy: fail. Please fix clang-tidy findings.
clang-format: pass.
Build artifacts: diff.json, clang-tidy.txt, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
Unit tests: pass. 61237 tests passed, 0 failed and 729 were skipped.
clang-tidy: fail. Please fix clang-tidy findings.
clang-format: pass.
Build artifacts: diff.json, clang-tidy.txt, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
Unit tests: pass. 61238 tests passed, 0 failed and 729 were skipped.
clang-tidy: fail. Please fix clang-tidy findings.
clang-format: pass.
Build artifacts: diff.json, clang-tidy.txt, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
Unit tests: pass. 61251 tests passed, 0 failed and 736 were skipped.
clang-tidy: fail. Please fix clang-tidy findings.
clang-format: pass.
Build artifacts: diff.json, clang-tidy.txt, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
lld/ELF/Options.td | ||
---|---|---|
225 | I"m confused. Doesn't "GCC 5.4 or earlier AND GCC 6.4 or earlier" just mean "GCC 5.4 or earlier"? |
lld/ELF/InputSection.cpp | ||
---|---|---|
980–984 | It can't. rel.sym->file == file is the case we want to ignore when --lax-call-lacks-nop is specified. So we use !(config->laxCallLacksNop && rel.sym->file == file) here. | |
lld/ELF/Options.td | ||
225 | Each major version has a release branch. This was fixed in 7 (not released at that time), then back ported to the release branches of 5 and 6. So certain 5.* and 6.* releases do not include the patch. |
Unit tests: fail. 61245 tests passed, 6 failed and 736 were skipped.
failed: LLVM-Unit.ADT/_/ADTTests/APFloatTest.DecimalStringsWithoutNullTerminators failed: Clang Tools.clang-tidy/checkers/readability-magic-numbers-bitfields.cpp failed: Clang Tools.clang-tidy/checkers/readability-magic-numbers.cpp failed: Clang Tools.clang-tidy/readability-magic-numbers-userliteral.cpp failed: libc++.std/thread/thread_mutex/thread_mutex_requirements/thread_mutex_requirements_mutex/thread_mutex_recursive/lock.pass.cpp failed: libc++.std/thread/thread_mutex/thread_mutex_requirements/thread_mutex_requirements_mutex/thread_mutex_recursive/try_lock.pass.cpp
clang-tidy: fail. Please fix clang-tidy findings.
clang-format: pass.
Build artifacts: diff.json, clang-tidy.txt, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
Thanks for doing this. I think this approach in much safer at the cost of some friction on the systems where the option is needed. My one suggestion would be to separate the tail call case b foo from the normal call case. It will cause a runtime failure if the callers caller resides outside the dso and would be much more likely then a failure like glibc encountered. I believe gcc/gfortran got that case correct so it shouldn't impact usability on the older OS releases, but I'm not 100% sure of that.
clang-tidy: warning: invalid case style for member 'emitLLVM' [readability-identifier-naming]