[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #10 from CVS Commits --- The master branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:87ca615aa6f400c64d0bf13088c0ffdd14e22830 commit r10-6130-g87ca615aa6f400c64d0bf13088c0ffdd14e22830 Author: Andrew Pinski Date:

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 Andrew Pinski changed: What|Removed |Added Keywords||patch Status|NEW

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 Andrew Pinski changed: What|Removed |Added Attachment #47663|0 |1 is obsolete|

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #7 from Andrew Pinski --- So looking further, my patch is incorrect. The glibc sources for __tls_get_addr says it returns void* which is a 32bit value which might or might not be zero extended. So I need to fix this slightly

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #6 from Andrew Pinski --- (In reply to Andrew Pinski from comment #5) > Created attachment 47663 [details] > Patch which fixes the problem > > So we need to accept P modes and not PTR modes for the aarch64_valid_symref. > And then

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #5 from Andrew Pinski --- Created attachment 47663 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47663=edit Patch which fixes the problem So we need to accept P modes and not PTR modes for the aarch64_valid_symref. And then

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #4 from Andrew Pinski --- (In reply to Richard Earnshaw from comment #3) > I don't think that's right either. These are supposed to be machine > addresses, not C pointers. HMm, you might be right. I will take a look over the

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #3 from Richard Earnshaw --- (In reply to Andrew Pinski from comment #2) > Simplier patch, change PTR to P instead. Mine then. > > That is: > diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md > index

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119 --- Comment #1 from Peakulorain --- Here is my patch to fix this program. diff -Nurp a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md --- a/gcc/config/aarch64/aarch64.md 2019-12-20 03:16:50.706754343 +0800 +++