public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94254] [10 regression] r10-7312 causes compiler hangs Date: Sun, 22 Mar 2020 09:30:47 +0000 [thread overview] Message-ID: <bug-94254-4-fQtufKlwqB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94254-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94254 --- Comment #2 from Zdenek Sojka <zsojka at seznam dot cz> --- (In reply to Zdenek Sojka from comment #1) > I observe the same issue, and it breaks libgcc build for me: ... > > (for reasons unknown to me, git gcc-descr returns "r10-7320" for me for the > same git checkout as in #c0) Sorry, I accidentally sent the message before I removed this part of the comment; apparently git gcc-descr works with the most recent commit in the branch, not with the actual checkout.
next prev parent reply other threads:[~2020-03-22 9:30 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-21 20:52 [Bug target/94254] New: " seurer at linux dot vnet.ibm.com 2020-03-22 9:27 ` [Bug target/94254] " zsojka at seznam dot cz 2020-03-22 9:30 ` zsojka at seznam dot cz [this message] 2020-03-22 17:11 ` rsandifo at gcc dot gnu.org 2020-03-22 18:30 ` rsandifo at gcc dot gnu.org 2020-03-22 18:39 ` rsandifo at gcc dot gnu.org 2020-03-22 19:03 ` zsojka at seznam dot cz 2020-03-22 19:05 ` rsandifo at gcc dot gnu.org 2020-03-23 1:19 ` segher at gcc dot gnu.org 2020-03-23 8:07 ` rguenth at gcc dot gnu.org 2020-03-23 10:20 ` rsandifo at gcc dot gnu.org 2020-03-23 12:35 ` segher at gcc dot gnu.org 2020-03-23 13:43 ` rsandifo at gcc dot gnu.org 2020-03-23 15:17 ` segher at gcc dot gnu.org 2020-03-23 18:30 ` rsandifo at gcc dot gnu.org 2020-03-23 18:33 ` zsojka at seznam dot cz 2020-03-24 10:36 ` segher at gcc dot gnu.org 2020-03-24 10:41 ` segher at gcc dot gnu.org 2020-03-25 11:06 ` doko at debian dot org 2020-03-25 16:35 ` law at redhat dot com 2020-03-25 16:38 ` cvs-commit at gcc dot gnu.org 2020-03-25 16:38 ` law at redhat dot com
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-94254-4-fQtufKlwqB@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).