about summary refs log tree commit diff
path: root/library/std/src/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorMatthew Maurer <matthew.r.maurer@gmail.com>2020-04-16 19:40:11 -0700
committerMatthew Maurer <matthew.r.maurer@gmail.com>2020-04-29 13:38:59 -0700
commit0e7d5be4b808bd7ccb1d45aa8f7e5026a15aee93 (patch)
treef96a66037263baa82b0267d9f450eb09c1799a4f /library/std/src/sys/unix/stack_overflow.rs
parent825cf51ad7d2578fcd60a0b7b107d7b0ab3017ff (diff)
downloadrust-0e7d5be4b808bd7ccb1d45aa8f7e5026a15aee93.tar.gz
rust-0e7d5be4b808bd7ccb1d45aa8f7e5026a15aee93.zip
Use .init_array rather than .ctors
LLVM TargetMachines default to using the (now-legacy) .ctors
representation of init functions. Mixing .ctors and .init_array
representations can cause issues when linking with lld.

This happens in practice for:

* Our profiling runtime which is currently implicitly built with
  .init_array since it is built by clang, which sets this field.
* External C/C++ code that may be linked into the same process.

To support legacy systems which may use .ctors, targets may now specify
that they use .ctors via the use_ctors attribute which defaults to
false.

For debugging and manual control, -Z use-ctors-section=yes/no will allow
manual override.

Fixes: #71233
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions