Date: Thu, 17 Oct 2024 14:26:46 -0400
Em qua., 16 de out. de 2024 às 19:28, Nathan Sidwell via SG15 <
sg15_at_[hidden]> escreveu:
> > It is important to note that, in the Itanium ABI, even if the module
> doesn’t currently have
> > anything that needs static initialization, the translation unit
> importing that module will still
> > generate the code to call the initializer, because we don’t want the
> addition of a static initializer
> > to a shared object to result in an ABI break
> this is false.
Interesting. That is the current implementation in clang, IIUC.
We probably need to clarify that point, because it is indeed problematic if
adding a new static initializer means an ABI breakage for the library.
daniel
sg15_at_[hidden]> escreveu:
> > It is important to note that, in the Itanium ABI, even if the module
> doesn’t currently have
> > anything that needs static initialization, the translation unit
> importing that module will still
> > generate the code to call the initializer, because we don’t want the
> addition of a static initializer
> > to a shared object to result in an ABI break
> this is false.
Interesting. That is the current implementation in clang, IIUC.
We probably need to clarify that point, because it is indeed problematic if
adding a new static initializer means an ABI breakage for the library.
daniel
Received on 2024-10-17 18:26:59