Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [5 earlier articles] |
| Re: binary search debugging of compilers gah4@u.washington.edu (gah4) (2023-05-14) |
| Re: binary search debugging of compilers cameron.mcinally@nyu.edu (Cameron McInally) (2023-05-14) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-15) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-15) |
| Re: binary search debugging of compilers gah4@u.washington.edu (gah4) (2023-05-16) |
| Re: binary search debugging of compilers rsc@swtch.com (Russ Cox) (2023-05-17) |
| Re: binary search debugging of compilers cameron.mcinally@nyu.edu (Cameron McInally) (2023-05-17) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-17) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-17) |
| Re: binary search debugging of compilers gah4@u.washington.edu (gah4) (2023-05-17) |
| Re: binary search debugging of compilers spibou@gmail.com (Spiros Bousbouras) (2023-05-18) |
| Re: binary search debugging of compilers rsc@swtch.com (Russ Cox) (2023-05-18) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-19) |
| [6 later articles] |
| From: | Cameron McInally <cameron.mcinally@nyu.edu> |
| Newsgroups: | comp.compilers |
| Date: | Wed, 17 May 2023 13:40:33 -0400 |
| Organization: | Compilers Central |
| References: | <CADSkJJVN7RGqhgVDZaz_K5be6uEDaMofMu5OF3RR4Y5-fDu00Q@mail.gmail.com> 23-05-013 |
| Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="32179"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | debug, tools |
| Posted-Date: | 17 May 2023 13:44:53 EDT |
| In-Reply-To: | 23-05-013 |
On Wed, May 17, 2023 at 13:13 Russ Cox <rsc@swtch.com> wrote:
> Thanks to everyone for the replies and pointers.
>
> As far as 'git bisect' is concerned, we have found 'git bisect'
> incredibly useful too, of course. It is clearly another instance of
> binary search to find bugs, but it is binary search over time, while
> the system I described is binary search over the program being
> compiled. "What change broke the compiler?" vs "What code does that
> change miscompile?". The two are independent and complementary.
As for a binary search over the program being compiled, LLVM has a
mechanism to bisect optimization passes. Not exactly the same, but worth
noting.
https://llvm.org/docs/OptBisect.html
Also, Viet is still in compilers at Coherent Logix.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.