Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| binary search debugging of compilers rsc@swtch.com (Russ Cox) (2023-05-12) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-13) |
| Re: binary search debugging of compilers pronesto@gmail.com (Fernando) (2023-05-13) |
| Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-14) |
| Re: binary search debugging of compilers tkoenig@netcologne.de (Thomas Koenig) (2023-05-14) |
| 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) |
| [13 later articles] |
| From: | Thomas Koenig <tkoenig@netcologne.de> |
| Newsgroups: | comp.compilers |
| Date: | Sun, 14 May 2023 19:59:21 -0000 (UTC) |
| Organization: | news.netcologne.de |
| References: | 23-05-003 |
| Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="85036"; mail-complaints-to="abuse@iecc.com" |
| Keywords: | debug, tools |
| Posted-Date: | 14 May 2023 22:41:57 EDT |
Russ Cox <rsc@swtch.com> schrieb:
> As I mentioned at the top, I am interested to hear about earlier uses
> of approaches like this, or any other ideas for situations where the
> approach might be applicable. Clearly the general problem has overlaps
> with group testing [1], and in particular Hwang's binary search-based
> approach (1972) [2].
For GCC regression-hunting, two techniques are routinely used.
One of them is the use of "gcc bisect", described at
https://git-scm.com/docs/git-bisect . If there is a failing test
case, this can (at the cost of some CPU time) usually pinpoint
offending commit.
For reducing test cases, at least for C and C++, cvise
https://github.com/marxin/cvise is now the mehod of choice; it is
brutally efficient at reducing test cases to an absolute minimum.
Because it can transform C and C++ programs, it can make
transformations of the program which are language-aware.
Both are tools external to the compiler.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.