public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/95577] Tcl error with testsuite/gcc.misc-tests/outputs.exp on darwin Date: Tue, 23 Jun 2020 11:17:41 +0000 [thread overview] Message-ID: <bug-95577-4-laJzeu9qpA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95577-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95577 Alexandre Oliva <aoliva at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |aoliva at gcc dot gnu.org --- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- Iain, Do platforms that use dsymutil support -gsplit-dwarf? I'm thinking of bringing -g into the gsplit_dwarf variable, so it won't be enable without -gsplit-dwarf, and removing other explicit mentions of -g from outputs.exp. Would this be enough to address the dsymutil left-overs?
next prev parent reply other threads:[~2020-06-23 11:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 14:24 [Bug testsuite/95577] New: " dominiq at lps dot ens.fr 2020-06-08 15:06 ` [Bug testsuite/95577] " iains at gcc dot gnu.org 2020-06-09 7:36 ` iains at gcc dot gnu.org 2020-06-23 11:17 ` aoliva at gcc dot gnu.org [this message] 2020-06-23 11:45 ` iains at gcc dot gnu.org 2020-06-23 13:16 ` aoliva at gcc dot gnu.org 2020-06-23 13:31 ` iains at gcc dot gnu.org 2020-06-23 13:58 ` aoliva at gcc dot gnu.org 2020-06-23 16:42 ` dominiq at lps dot ens.fr 2020-06-24 20:24 ` cvs-commit at gcc dot gnu.org 2020-06-24 20:41 ` aoliva 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-95577-4-laJzeu9qpA@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: linkBe 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).