From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 750DB3851416; Tue, 30 Mar 2021 07:31:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 750DB3851416
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-99694-4-kvRs2Z0uqy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-99694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-99694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Mar 2021 07:31:59 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D99694

--- Comment #8 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
(In reply to Haoxin Tu from comment #7)
> (In reply to Martin Li=C5=A1ka from comment #1)
> > Confirmed, started with r9-7156-g33579b59aaf02eb7.
>=20
> 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.

>=20=20
> As far as I know, we can use git bitset to set a bad and good commit to t=
hen
> apply binary search to find the exact place that caused the error(I usual=
ly
> 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?=20

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.

>=20
> Also, I am wondering if you are using an automatic tool or other approach=
es
> that can quickly find the bad commit to cause the problem. If I learned h=
ow
> to do this quickly, I'd like to do the bitset myself and tell the bad com=
mit
> when I submit a report next time.
>=20
> 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

>=20
>=20
> Best,
> Haoxin=