]>
Commit | Line | Data |
---|---|---|
2b03887a | 1 | use crate::spec::{Cc, FramePointer, LinkerFlavor, Lld, StackProbeType, Target}; |
7453a54e | 2 | |
29967ef6 | 3 | pub fn target() -> Target { |
a7813a04 | 4 | let mut base = super::linux_musl_base::opts(); |
5e7ed085 | 5 | base.cpu = "pentium4".into(); |
c30ab7b3 | 6 | base.max_atomic_width = Some(64); |
2b03887a FG |
7 | base.add_pre_link_args(LinkerFlavor::Gnu(Cc::Yes, Lld::No), &["-m32", "-Wl,-melf_i386"]); |
8 | base.stack_probes = StackProbeType::X86; | |
7453a54e | 9 | |
32a655c1 SL |
10 | // The unwinder used by i686-unknown-linux-musl, the LLVM libunwind |
11 | // implementation, apparently relies on frame pointers existing... somehow. | |
12 | // It's not clear to me why nor where this dependency is introduced, but the | |
13 | // test suite does not pass with frame pointers eliminated and it passes | |
14 | // with frame pointers present. | |
15 | // | |
16 | // If you think that this is no longer necessary, then please feel free to | |
17 | // ignore! If it still passes the test suite and the bots then sounds good | |
18 | // to me. | |
19 | // | |
20 | // This may or may not be related to this bug: | |
21 | // https://llvm.org/bugs/show_bug.cgi?id=30879 | |
136023e0 | 22 | base.frame_pointer = FramePointer::Always; |
32a655c1 | 23 | |
29967ef6 | 24 | Target { |
5e7ed085 | 25 | llvm_target: "i686-unknown-linux-musl".into(), |
29967ef6 | 26 | pointer_width: 32, |
dfeec247 XL |
27 | data_layout: "e-m:e-p:32:32-p270:32:32-p271:32:32-p272:64:64-\ |
28 | f64:32:64-f80:32-n8:16:32-S128" | |
5e7ed085 FG |
29 | .into(), |
30 | arch: "x86".into(), | |
7453a54e | 31 | options: base, |
29967ef6 | 32 | } |
7453a54e | 33 | } |