Explain what happens for PE targeted linkers in the case where the user actually tries to provide __CTOR_LIST__ and/or __DTOR_LIST__ symbols.
* scripttempl/pe.sc: Improve the comment about overriding __CTOR_LIST__ and __DTOR_LIST__ symbols. * scripttemp/pep.sc: Likewise.
This commit is contained in:
parent
8f9ea98beb
commit
99f8774cca
|
@ -1,3 +1,9 @@
|
||||||
|
2018-08-07 Martin Storsjo <martin@martin.st>
|
||||||
|
|
||||||
|
* scripttempl/pe.sc: Improve the comment about overriding
|
||||||
|
__CTOR_LIST__ and __DTOR_LIST__ symbols.
|
||||||
|
* scripttemp/pep.sc: Likewise.
|
||||||
|
|
||||||
2018-08-07 Nick Clifton <nickc@redhat.com>
|
2018-08-07 Nick Clifton <nickc@redhat.com>
|
||||||
|
|
||||||
* po/bg.po: Updated Bulgarian translation.
|
* po/bg.po: Updated Bulgarian translation.
|
||||||
|
|
|
@ -106,10 +106,12 @@ SECTIONS
|
||||||
overridden and global constructors will not be run.
|
overridden and global constructors will not be run.
|
||||||
|
|
||||||
This does mean that it is not possible for a user to define
|
This does mean that it is not possible for a user to define
|
||||||
their own __CTOR_LIST__ and __DTOR_LIST__ symbols. If that
|
their own __CTOR_LIST__ and __DTOR_LIST__ symbols; if they do,
|
||||||
ability is needed a custom linker script will have to be
|
the content from those variables are included but the symbols
|
||||||
used. (The custom script can just be a copy of this script
|
defined here silently take precedence. If they truly need to
|
||||||
with the PROVIDE() qualifiers added).
|
be redefined, a custom linker script will have to be used.
|
||||||
|
(The custom script can just be a copy of this script with the
|
||||||
|
PROVIDE() qualifiers added).
|
||||||
|
|
||||||
See PR 22762 for more details. */
|
See PR 22762 for more details. */
|
||||||
___CTOR_LIST__ = .;
|
___CTOR_LIST__ = .;
|
||||||
|
|
|
@ -107,10 +107,12 @@ SECTIONS
|
||||||
overridden and global constructors will not be run.
|
overridden and global constructors will not be run.
|
||||||
|
|
||||||
This does mean that it is not possible for a user to define
|
This does mean that it is not possible for a user to define
|
||||||
their own __CTOR_LIST__ and __DTOR_LIST__ symbols. If that
|
their own __CTOR_LIST__ and __DTOR_LIST__ symbols; if they do,
|
||||||
ability is needed a custom linker script will have to be
|
the content from those variables are included but the symbols
|
||||||
used. (The custom script can just be a copy of this script
|
defined here silently take precedence. If they truly need to
|
||||||
with the PROVIDE() qualifiers added).
|
be redefined, a custom linker script will have to be used.
|
||||||
|
(The custom script can just be a copy of this script with the
|
||||||
|
PROVIDE() qualifiers added).
|
||||||
|
|
||||||
See PR 22762 for more details. */
|
See PR 22762 for more details. */
|
||||||
___CTOR_LIST__ = .;
|
___CTOR_LIST__ = .;
|
||||||
|
|
Loading…
Reference in New Issue