public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pkubaj at anongoth dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/89494] Bootstrap error when using GCC 4.2.1 Date: Sun, 12 Apr 2020 11:18:42 +0000 [thread overview] Message-ID: <bug-89494-4-bFELuhp3mJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89494-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89494 Piotr Kubaj <pkubaj at anongoth dot pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.sandiford at arm dot com --- Comment #15 from Piotr Kubaj <pkubaj at anongoth dot pl> --- CC'ing richard.sandiford@arm.com, whose one of commits broke building of GCC 10 with GCC 4.2. I'm still bisecting, but it was one of those commits, all by richard.sandiford@arm.com: pkubaj@talos:$/usr/home/pkubaj/gcc$ git bisect view | grep commit commit cf0d189eb989906d17010ca7c0b07f1763d5fde5 commit 634afa05a8cbff010480088811fe1f39eca70c1d commit b12cdd6e8e8dd1f39a941b731ba1056d656a094f commit 0ffef2005fd7536efbc9c3a572701998c8a8080c commit 7256c7194e186fce6ff866a124a77b08196c2a5f commit 6930c98c69ad695469ee7daa74b3b6d578afdd0d commit 6783fdb7057d559aa1da8afa2c15a702c532a03e commit e7056ca417326a70eca05defb6a8b20b737d3417 commit 52090e4dbd064f486af606e3f8a283dbddc7c18a commit a7c81bc1fb43366ca1b4332d8a6042b648a84cdc commit 4f53599cb5b822cd7f95997861c2e064977ecb6a
next prev parent reply other threads:[~2020-04-12 11:18 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89494-4@http.gcc.gnu.org/bugzilla/> 2020-04-11 3:15 ` pkubaj at anongoth dot pl 2020-04-11 18:02 ` pkubaj at anongoth dot pl 2020-04-11 18:08 ` pkubaj at anongoth dot pl 2020-04-12 11:18 ` pkubaj at anongoth dot pl [this message] 2020-04-12 15:54 ` pkubaj at anongoth dot pl 2020-04-14 20:36 ` jakub at gcc dot gnu.org 2020-04-14 21:08 ` iains at gcc dot gnu.org 2020-04-14 21:13 ` jakub at gcc dot gnu.org 2020-04-15 12:20 ` jakub at gcc dot gnu.org 2020-04-15 13:17 ` cvs-commit at gcc dot gnu.org 2020-04-15 13:42 ` pkubaj at anongoth dot pl 2020-04-15 14:46 ` jakub at gcc dot gnu.org 2020-04-16 8:16 ` cvs-commit at gcc dot gnu.org 2020-05-01 1:36 ` pkubaj at anongoth dot pl 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2021-03-24 20:03 ` iains at gcc dot gnu.org 2021-03-24 20:55 ` pkubaj at anongoth dot pl 2021-03-24 21:12 ` iains at gcc dot gnu.org 2021-04-10 17:03 ` pkubaj at anongoth dot pl 2024-03-17 4:18 ` iains at gcc dot gnu.org 2024-03-17 10:45 ` pkubaj at anongoth dot pl 2024-03-17 19:00 ` pinskia 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-89494-4-bFELuhp3mJ@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).