Hi, I'm trying to create a global variable in my own PASS which
located at the LATE_IPA_PASSES. (I'm using GCC 10.3.0.)
And after creating it, I added the attributes like the following.
// 1. create the var
tree new_name = get_identifier (xx);
tree new_type = build_pointer_type (xx);
tree new_var
I feel like I have asked this before. Currently, GCC uses calls to
__tls_get_addr to obtain the address of global-dynamic TLS variables.
On other architectures with support for GNU2 TLS descriptors, those are
used by default.
Should we flip the default to GNU2 descriptors? Support has been
avail
On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc wrote:
>
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
I am getting this failure to build from clean trunk.
In file included from ../../../../trunk/libgomp/config/linux/allocator.c:31:
../../../../trunk/libgomp/config/linux/allocator.c: In function
‘linux_memspace_alloc’:
../../../../trunk/libgomp/config/linux/allocator.c:70:26: error: format
‘%ld’
Hi!
On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
> I am getting this failure to build from clean trunk.
This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd
"libgomp: basic pinned memory on Linux", which supposedly was only tested
with '--disable-multilib' or so. As A
Florian Weimer via Gcc writes:
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
>
> Should we flip the defaul
Hi!
On 2023-12-13T20:36:40+0100, I wrote:
> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
>> I am getting this failure to build from clean trunk.
>
> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd
> "libgomp: basic pinned memory on Linux", which supposedly was only
On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
> Hi!
>
> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
> > I am getting this failure to build from clean trunk.
>
> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd
> "libgomp: basic pinned memory on Linux", which
Hi!
On 2023-12-13T20:27:44+, Jonathan Wakely wrote:
> On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
>> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
>> > I am getting this failure to build from clean trunk.
>>
>> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172
On Wed, 13 Dec 2023 at 20:56, Thomas Schwinge wrote:
>
> Hi!
>
> On 2023-12-13T20:27:44+, Jonathan Wakely wrote:
> > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote:
> >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote:
> >> > I am getting this failure to build from clean trunk.
> >>
>
On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc wrote:
>
> I feel like I have asked this before. Currently, GCC uses calls to
> __tls_get_addr to obtain the address of global-dynamic TLS variables.
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
On Wed, Dec 13, 2023 at 1:08 PM Andrew Pinski wrote:
>
> On Wed, Dec 13, 2023 at 6:19 AM Florian Weimer via Gcc
> wrote:
> >
> > I feel like I have asked this before. Currently, GCC uses calls to
> > __tls_get_addr to obtain the address of global-dynamic TLS variables.
> > On other architecture
On 2023/12/12 07:43 UTC+8, Jeff Law via Gcc wrote:
On 12/11/23 16:19, Andrew Pinski via Gcc wrote:
nds32 support in Linux was removed last year:
https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
The support for glibc never made it upstream as far as I can tell either.
What are others th
On 2023/12/12 07:43 UTC+8, Jeff Law via Gcc wrote:
On 12/11/23 16:19, Andrew Pinski via Gcc wrote:
nds32 support in Linux was removed last year:
https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
The support for glibc never made it upstream as far as I can tell either.
What are others th
Florian Weimer via Gcc writes:
> [...]
> On other architectures with support for GNU2 TLS descriptors, those are
> used by default.
>
It looks like arm32 defaults to gnu, not gnu2. andrew mentioned fdpic
will be an issue there but maybe we could carve that out.
> Should we flip the default to
Hi Richard,
Thanks a lot for your response!
Another failure reported by the Linaro CI is as follows:
Running gcc:gcc.dg/dg.exp ...
FAIL: gcc.dg/ira-shrinkwrap-prep-1.c scan-rtl-dump pro_and_epilogue "Performing
shrink-wrapping"
FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing
s
16 matches
Mail list logo
