Ping.

Updated patch based on previous comments.

Patch updated from comments, main changes are:

I will update the patch, since it is incomplete and requires https://reviews.llvm.org/D94809 .

Updated patch based on previous version.

Both https://reviews.llvm.org/D93044 and https://reviews.llvm.org/D93235 have been approved, so the prerequisites of this patch are ok to land.

In D93235#2454115, @grimar wrote:

LGTM with 2 minor nits. Thanks!

Updated patch based on previous comment:

Updated patch based on previous comments:

Updated patch based on previous comments. It depends on https://reviews.llvm.org/D93235 for YAML STO_AARCH64_VARIANT_PCS support.

Updated patch based on previous comment.

Updated patch based on previous comments. For in.relaIplt / R_AARCH64_IRELATIVE
I decided to not include since it seems to what binutils is done currently. I will raise with
them if this is the intended behaviour or if R_AARCH64_IRELATIVE should also create
the dynamic tag (and fix is accordingly on lld if it were the case).

Updated patch based on previous comments.

Updated patch based on previous comments.

Updated patch based on previous comments.

In D93045#2446599, @MaskRay wrote:

st_other marked with STO_AARCH64_VARIANT_PCS indicates a may follow a variant

a -> it

In D92241#2421377, @MaskRay wrote:

Is https://reviews.llvm.org/D91733#2407055 resolved?

In D91733#2407055, @wolfgangp wrote:

Isn't COMPILER_RT_HAS_FLOAT16 generated using the host compiler? If so, using the same flag for a compiler_rt test could fail if the host compiler supports f16 and the target compiler does not.

In D91732#2404933, @ostannard wrote:

LGTM

Also, __fp16 is a storage format and promoted to 'float' for argument passing

It doesn't affect this patch, but for all of the ARM and AArch64 ABIs, __fp16 arguments are passed in the bottom half of an integer or FP register, not promoted to float. There was an old version of the AArch32 ABI (I think) which did that, but I don't think any compiler implemented it before it was changed.

In D90175#2402021, @ostannard wrote:

They are enabled iff the compiler supports _Float16.

Why are these not enabled for compilers which don't support _Float16? There is also the __fp16 type, which has been supported for much longer and could also generate code like this.

In D90175#2401747, @MaskRay wrote:

Apologies for my slow response.

Patches need to have a large context (see https://llvm.org/docs/Phabricator.html#requesting-a-review-via-the-web-interface I prefer arc diff)

Ping (x2).

Ping.

Ping.

Ping (x3).

Ping (x2).

Ping.

Ping.

I have adapted the news files using clang-format and fixed minor style issues pointed by previous comments.

Updated patch based on previous comments.

Hi atrosinenko, do you think this patch need any more change on the testing side?
The fp_lib.h/int_lib.h change would most likely require in a more complex without
much gain in organization imho.

Updated version based on previous comments.

In D83134#2225283, @vitalybuka wrote:

Is this patch still needed?

In D83134#2133857, @eugenis wrote:

Is unwinding actually broken on an all-clang, all-thumb system?

In D72449#1812818, @arichardson wrote:

I'm fine with this workaround although I'm very surprised that the test is not working. Especially since deterministic-archive.test and replace-update.test also set TZ to get reproducible output

Do you have access to any of the failing bots? If so what happens there if you change the TZ variable?
I get the following on all systems I have access to when I run something like date && date -u && env TZ=CET date && env TZ=CET date -u && env TZ=BST date && env TZ=BST date -u I get the following output:

Thu  9 Jan 2020 20:18:10 GMT
Thu  9 Jan 2020 20:18:10 UTC
Thu  9 Jan 2020 21:18:10 CET
Thu  9 Jan 2020 20:18:10 UTC
Thu  9 Jan 2020 20:18:10 UTC
Thu  9 Jan 2020 20:18:10 UTC