public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libbacktrace/96973] No backtrace for cc1 on x86_64-apple-darwin Date: Wed, 09 Sep 2020 02:23:16 +0000 [thread overview] Message-ID: <bug-96973-4-WMOIFOSMBZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96973-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96973 --- Comment #12 from Ian Lance Taylor <ian at airs dot com> --- Thanks, that part should now be fixed also.
prev parent reply other threads:[~2020-09-09 2:23 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-08 10:48 [Bug libbacktrace/96973] New: " fxcoudert at gcc dot gnu.org 2020-09-08 10:52 ` [Bug libbacktrace/96973] " fxcoudert at gcc dot gnu.org 2020-09-08 11:19 ` fxcoudert at gcc dot gnu.org 2020-09-08 11:43 ` fxcoudert at gcc dot gnu.org 2020-09-08 12:32 ` fxcoudert at gcc dot gnu.org 2020-09-08 12:57 ` iains at gcc dot gnu.org 2020-09-08 15:28 ` iains at gcc dot gnu.org 2020-09-08 15:32 ` fxcoudert at gcc dot gnu.org 2020-09-08 20:20 ` cvs-commit at gcc dot gnu.org 2020-09-08 21:06 ` ian at airs dot com 2020-09-08 22:05 ` fxcoudert at gcc dot gnu.org 2020-09-09 2:12 ` cvs-commit at gcc dot gnu.org 2020-09-09 2:23 ` ian at airs dot com [this message]
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-96973-4-WMOIFOSMBZ@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).