File: clang-rust-target.patch

package info (click to toggle)
chromium 134.0.6998.35-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 5,929,812 kB
  • sloc: cpp: 34,189,808; ansic: 7,041,458; javascript: 4,034,221; python: 1,459,275; asm: 846,276; xml: 726,550; pascal: 178,372; sh: 104,683; objc: 91,089; perl: 88,388; sql: 48,244; cs: 43,980; makefile: 28,768; fortran: 24,137; php: 20,829; ruby: 17,806; tcl: 10,142; yacc: 8,631; lisp: 3,097; lex: 1,327; ada: 727; awk: 329; jsp: 228; sed: 36
file content (23 lines) | stat: -rw-r--r-- 792 bytes parent folder | download | duplicates (3) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 
Author: Daniel Richard G. <skunk@iSKUNK.ORG>

On amd64, Clang defaults to generating x86_64-pc-linux-gnu, while Rust
generates x86_64-unknown-linux-gnu. When ThinLTO is enabled, this leads
to link errors of the form

  ld.lld-16: error: Linking two modules of different target triples:
  $C_CXX_OBJECT is 'x86_64-pc-linux-gnu' whereas $RUST_OBJECT is
  'x86_64-unknown-linux-gnu'

--- a/build/config/linux/BUILD.gn
+++ b/build/config/linux/BUILD.gn
@@ -27,6 +27,10 @@ config("compiler") {
       asmflags += [ "-mbranch-protection=pac-ret" ]
     }
   }
+  if (current_cpu == "x64") {
+    # Match Rust output target (i.e. not x86_64-pc-linux-gnu)
+    cflags = [ "--target=x86_64-unknown-linux-gnu" ]
+  }
 }
 
 # This is included by reference in the //build/config/compiler:runtime_library