public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99694] [9 Regression] gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os since r9-7156-g33579b59aaf02eb7 Date: Tue, 30 Mar 2021 07:31:59 +0000 [thread overview] Message-ID: <bug-99694-4-kvRs2Z0uqy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99694-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99694 --- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to Haoxin Tu from comment #7) > (In reply to Martin Liška from comment #1) > > Confirmed, started with r9-7156-g33579b59aaf02eb7. > > Hi Martin. I am sorry to bother you, and I just have a question about how to > find a bad commit quickly in GCC. Hello. You don't have to find a bad revision, we can easily do that. > > As far as I know, we can use git bitset to set a bad and good commit to then > apply binary search to find the exact place that caused the error(I usually > do like this). My question is, is this means I should always find a commit > (to be tested), then build the source code and run the given test case to > tell a bad/good result? My concern is that build a GCC from a source code > may take a relatively long time (maybe more than half an hour), so if the > number of commits is much, it will take a long time to find the error > commit. Is my understanding correct or not? I have a script which I use: https://github.com/marxin/script-misc/blob/master/gcc-bisect.py I can do quick bisection as I have built binaries for all GCC revisions for a couple last years. > > Also, I am wondering if you are using an automatic tool or other approaches > that can quickly find the bad commit to cause the problem. If I learned how > to do this quickly, I'd like to do the bitset myself and tell the bad commit > when I submit a report next time. > > Please correct me if I am wrong and any suggestions are welcome! Thank you > very much! We thank you for a nice bug report. Keep doing :) Martin > > > Best, > Haoxin
next prev parent reply other threads:[~2021-03-30 7:31 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-21 13:48 [Bug c/99694] New: gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os haoxintu at gmail dot com 2021-03-22 8:14 ` [Bug middle-end/99694] [9/10/11 Regression] gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os since r9-7156-g33579b59aaf02eb7 marxin at gcc dot gnu.org 2021-03-22 8:32 ` jakub at gcc dot gnu.org 2021-03-22 9:05 ` rguenth at gcc dot gnu.org 2021-03-22 13:37 ` cvs-commit at gcc dot gnu.org 2021-03-22 13:38 ` [Bug middle-end/99694] [9/10 " rguenth at gcc dot gnu.org 2021-03-24 14:26 ` cvs-commit at gcc dot gnu.org 2021-03-28 3:27 ` [Bug middle-end/99694] [9 " haoxintu at gmail dot com 2021-03-30 7:31 ` marxin at gcc dot gnu.org [this message] 2021-04-12 11:23 ` cvs-commit at gcc dot gnu.org 2021-04-12 11:24 ` rguenth at gcc dot gnu.org 2021-08-04 8:31 ` haoxintu at gmail dot com 2021-08-04 8:45 ` marxin at gcc dot gnu.org 2021-08-04 8:50 ` haoxintu at gmail dot com 2021-08-04 11:37 ` rguenth at gcc dot gnu.org 2021-08-04 11:51 ` jakub at gcc dot gnu.org 2021-08-04 12:42 ` marxin at gcc dot gnu.org 2021-08-04 13:19 ` haoxintu at gmail 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-99694-4-kvRs2Z0uqy@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).