public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/103577] d21 SIGSEGV on Darwin/x86_64 Date: Mon, 13 Dec 2021 12:26:23 +0000 [thread overview] Message-ID: <bug-103577-4-7WsWapgKA1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103577-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103577 --- Comment #3 from Iain Buclaw <ibuclaw at gdcproject dot org> --- FYI, with darwin, I've only been using the most recent commit in releases/gcc-11 for testing as there have been a number of issues exposed from that port. I have VMs set-up running 10.4 (PPC), 10.6 (x86_64), 10.13, 10.14, 10.15, 11, and 12. Not yet gotten round to building a bootstrap compiler from gcc-11 just yet though for testing build of master.
next prev parent reply other threads:[~2021-12-13 12:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-06 10:19 [Bug d/103577] New: " ro at gcc dot gnu.org 2021-12-13 12:09 ` [Bug d/103577] " ro at CeBiTec dot Uni-Bielefeld.DE 2021-12-13 12:23 ` ibuclaw at gdcproject dot org 2021-12-13 12:26 ` ibuclaw at gdcproject dot org [this message] 2021-12-13 12:54 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-12-13 12:56 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-12-15 9:25 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-103577-4-7WsWapgKA1@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).