Currently, the GNU/Linux ABI does not really specify whether the thread
pointer (the address of the TCB) may change at a function boundary.
Traditionally, GCC assumes that the ABI allows caching addresses of
thread-local variables across function calls. Such caching varies in
aggressiveness betwe
Hi Florian,
This also affects fibres implementations (both C++ and D ones at least from
discussion with both communities).
> On 20 Jul 2021, at 15:52, Florian Weimer via Gcc wrote:
>
> Currently, the GNU/Linux ABI does not really specify whether the thread
> pointer (the address of the TCB) may
On Fri, 11 Jun 2021, vincent Dupaquis wrote:
> I've got the feeling the GOT is not convinient and goes in opposite
> direction than the one we try to achieve with having PIC, at least this is the
> reason why I'm trying to avoid it.
>
> Any clue on the reason why it has been implemented t
On Fri, 11 Jun 2021, John Ericson wrote:
> I would like to propose that GNU tools consistently interpret configs
> with "netbsd" as meaning ELF as opposed to a.out. Currently, newer CPUs
> do that, but older ones have "netbsd" mean a.out for historical reasons,
> and "netbsdelf" is used instead
