2022-08-06 21:08:46 +03:00
|
|
|
use crate::spec::{Cc, FramePointer, LinkerFlavor, Lld, StackProbeType, Target};
|
2015-12-29 22:33:58 +00:00
|
|
|
|
2020-10-05 15:37:55 +03:00
|
|
|
pub fn target() -> Target {
|
2016-05-01 17:41:28 -04:00
|
|
|
let mut base = super::linux_musl_base::opts();
|
2022-03-22 11:43:05 +01:00
|
|
|
base.cpu = "pentium4".into();
|
2016-10-03 23:45:40 -05:00
|
|
|
base.max_atomic_width = Some(64);
|
2022-08-06 21:08:46 +03:00
|
|
|
base.add_pre_link_args(LinkerFlavor::Gnu(Cc::Yes, Lld::No), &["-m32", "-Wl,-melf_i386"]);
|
2022-09-29 19:13:30 -07:00
|
|
|
base.stack_probes = StackProbeType::X86;
|
2015-12-29 22:33:58 +00:00
|
|
|
|
2017-01-20 15:32:47 -08:00
|
|
|
// The unwinder used by i686-unknown-linux-musl, the LLVM libunwind
|
|
|
|
// implementation, apparently relies on frame pointers existing... somehow.
|
|
|
|
// It's not clear to me why nor where this dependency is introduced, but the
|
|
|
|
// test suite does not pass with frame pointers eliminated and it passes
|
|
|
|
// with frame pointers present.
|
|
|
|
//
|
|
|
|
// If you think that this is no longer necessary, then please feel free to
|
|
|
|
// ignore! If it still passes the test suite and the bots then sounds good
|
|
|
|
// to me.
|
|
|
|
//
|
|
|
|
// This may or may not be related to this bug:
|
|
|
|
// https://llvm.org/bugs/show_bug.cgi?id=30879
|
2021-06-26 23:53:35 +03:00
|
|
|
base.frame_pointer = FramePointer::Always;
|
2017-01-20 15:32:47 -08:00
|
|
|
|
2020-10-05 15:37:55 +03:00
|
|
|
Target {
|
2022-03-22 11:43:05 +01:00
|
|
|
llvm_target: "i686-unknown-linux-musl".into(),
|
2020-10-14 18:08:12 +02:00
|
|
|
pointer_width: 32,
|
2020-01-07 21:26:52 +01:00
|
|
|
data_layout: "e-m:e-p:32:32-p270:32:32-p271:32:32-p272:64:64-\
|
|
|
|
f64:32:64-f80:32-n8:16:32-S128"
|
2022-03-22 11:43:05 +01:00
|
|
|
.into(),
|
|
|
|
arch: "x86".into(),
|
2015-12-29 22:33:58 +00:00
|
|
|
options: base,
|
2020-10-05 15:37:55 +03:00
|
|
|
}
|
2015-12-29 22:33:58 +00:00
|
|
|
}
|