LGTM except a nit.

Address @DavidSpickett's comments.

In D145550#4177291, @DavidSpickett wrote:

Seems to me that member functions of ELFRelocation should use the typedefs from lldb/source/Plugins/ObjectFile/ELF/ELFHeader.h where there is one. elf_sxword for example.

If you want to do that in another patch, that's fine. Just in case some test case is relying on the uin64_t -> unsigned down cast unintentionally.

Address @DavidSpickett's comments.

1. Fix the && issue.
2. Make the test more readable.

Yes, I think the ISA's pseudo-code description is incorrect. Maybe it shoud be:

bytepick.w:

LGTM. Thanks.

Thanks for the improvements. LGTM. What do others think?

Address @vzakhari's comments and add LoongArch to more target-rewrite tests.

LGTM. Thanks!

Thanks. Overall LGTM except the handling of FeatureBits (maybe can be handled in a seperate patch) and some nits.

Verification result: llvm is successfully built/linked by clang/lld with this patch applied.

I just verified the latest change, lld still fail to link llvm and report the error:

ld.lld: error: relocation R_LARCH_PCALA_HI20 cannot be used against symbol '__cxa_atexit'; recompile with -fPIC                                                                              
>>> defined in /usr/lib64/libc.so.6
>>> referenced by atexit.c:46 (../stdlib/atexit.c:46)
>>>               atexit.oS:(atexit) in archive /usr/lib64/libc_nonshared.a
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.

Maybe should mention LLD in the title?

LGTM. Happy Chinese new year!

According to https://llvm.org/docs/HowToReleaseLLVM.html#release-patch-rules there might be 10 days (before RC1) for us. Hope we can finish it.

Does anyone know why patchable-function-entry is not documented in https://llvm.org/docs/LangRef.html#function-attributes?

In D141750#4053473, @MaskRay wrote:

pip3 install --user recommonmark sphinx # sphinx-automodapi for lldb

cmake ...

ninja ... docs-llvm-html

Fix the issue "Title underline too short" reported by sphinx-build.

In D141750#4053469, @SixWeining wrote:

I'm not sure if there is any format issue. Is there any way to verify? e.g. how to generate .html like https://llvm.org/docs/ReleaseNotes.html?

I'm not sure if there is any format issue. Is there any way to verify? e.g. how to generate .html like https://llvm.org/docs/ReleaseNotes.html?

Seems that missing atest in llvm/test/Instrumentation/MemorySanitizer/.

LGTM. Is there any objection?

Hi @thakis, LoongArch has been promoted to official target in D141191. Do you need to update gn build accordingly? (As I don't know how to verify.)

Expensive check fail https://lab.llvm.org/buildbot/#/builders/16/builds/41677. I will fix it as soon as possilbe or revert this change.

Thanks to all you guys to make things happen!

In D139582#4038394, @SixWeining wrote:

This change failed the https://github.com/llvm/llvm-test-suite/blob/main/SingleSource/Regression/C/gcc-c-torture/execute/pr59747.c (-O2/-O3) on many platforms including x86-64.

I think it is easy to reproduce:

clang -O2 pr59747.c
./a.out

This change failed the https://github.com/llvm/llvm-test-suite/blob/main/SingleSource/Regression/C/gcc-c-torture/execute/pr59747.c (-O2/-O3) on many platforms including x86-64.

Generally speaking ping is supposed to be once a week. But I ping now in order to have more time to resolve potential compiling or testing issues when the backend was exposed to other bots.

rebase