public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/101283] Several tests fail on Darwin with -gctf/gbtf
Date: Fri, 02 Jul 2021 14:50:43 +0000	[thread overview]
Message-ID: <bug-101283-4-SeP7ZELxWi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101283-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:

https://gcc.gnu.org/g:85017431068251628478f38346c273418c71209b

commit r12-1983-g85017431068251628478f38346c273418c71209b
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Fri Jul 2 09:51:57 2021 +0100

    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.

  parent reply	other threads:[~2021-07-02 14:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 11:42 [Bug debug/101283] New: Severaal test fail on Darwin with -gctf dominiq at lps dot ens.fr
2021-07-01 15:56 ` [Bug debug/101283] Several tests " cvs-commit at gcc dot gnu.org
2021-07-01 16:22 ` ibhagatgnu at gmail dot com
2021-07-01 16:32 ` iains at gcc dot gnu.org
2021-07-01 16:46 ` dominiq at lps dot ens.fr
2021-07-02  6:16 ` [Bug debug/101283] Several tests fail on Darwin with -gctf/gbtf rguenth at gcc dot gnu.org
2021-07-02  9:01 ` iains at gcc dot gnu.org
2021-07-02 14:50 ` cvs-commit at gcc dot gnu.org
2021-07-02 14:50 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-02 14:55 ` iains at gcc dot gnu.org
2021-07-02 15:13 ` iains at gcc dot gnu.org
2021-07-05 15:27 ` ibhagatgnu at gmail dot com
2021-07-05 20:42 ` iains at gcc dot gnu.org
2021-07-05 21:20 ` ibhagatgnu at gmail dot com
2021-07-06  0:47 ` cvs-commit at gcc dot gnu.org
2021-07-06  1:28 ` ibhagatgnu at gmail dot com
2021-07-06 21:08 ` cvs-commit at gcc dot gnu.org
2021-07-06 23:05 ` cvs-commit at gcc dot gnu.org
2021-07-06 23:14 ` cvs-commit at gcc dot gnu.org
2021-07-06 23:20 ` ibhagatgnu at gmail dot com
2021-07-09  1:51 ` dje at gcc dot gnu.org
2021-09-27 19:05 ` ibhagatgnu at gmail dot com
2021-09-27 19:09 ` iains at gcc dot gnu.org
2021-09-29 18:08 ` ibhagat at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101283-4-SeP7ZELxWi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).