aboutsummaryrefslogtreecommitdiff
path: root/gcc/expr.c
diff options
context:
space:
mode:
authorIain Sandoe <iain@sandoe.co.uk>2021-07-02 09:51:57 +0100
committerIain Sandoe <iain@sandoe.co.uk>2021-07-02 15:50:16 +0100
commit85017431068251628478f38346c273418c71209b (patch)
tree5ce40b874ff3a69547a1db978664556e21320982 /gcc/expr.c
parenteb817f27e82769aef545d580a0c47a3aa50d1ec4 (diff)
downloadgcc-85017431068251628478f38346c273418c71209b.zip
gcc-85017431068251628478f38346c273418c71209b.tar.gz
gcc-85017431068251628478f38346c273418c71209b.tar.bz2
Darwin, CTF, BTF: Do not run the DWARF debug link for BTF/CTF [PR101283].
Darwin uses an efficient two-stage process for debug linking. The static linker (ld64) notes the inputs required but does not link the debug. When required / on demand the debug is linked into a separate package by the debug linker (dsymutil). At present none of the Darwin tools consume or understand BTF/CTF. The static linker silently accepts the sections (but will not act on them as containing anything to be processed). However, the debug linker produces a warning that it has been presented with input with no [DWARF] debug content: warning: no debug symbols in executable (-arch x86_64). This causes several testsuite fails with excess errors. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> PR debug/101283 - Several tests fail on Darwin with -gctf/gbtf PR debug/101283 gcc/ChangeLog: * config/darwin.h (DSYMUTIL_SPEC): Do not try to run dsymutil for BTF/CTF.
Diffstat (limited to 'gcc/expr.c')
0 files changed, 0 insertions, 0 deletions