[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [csmith-dev] Any tricks for narrowing down GCC bugs to avoid duplications?
Another thing you can do is before submitting to GCC (or LLVM), take a
quick look at all open bugs submitted by me. For random reasons I do all
of our bug reporting.
On 04/21/2011 01:08 PM, Arthur O'Dwyer wrote:
Hi, csmith-dev! Long-time blog reader, first-time Csmith user.
My slightly-off-topic question is, does anyone have any specific
recommendations to avoid filing duplicate bugs against GCC?
My current list is pretty short:
* Use a bleeding-edge SVN checkout of GCC
* Check http://embed.cs.utah.edu/csmith/gcc-bugs.html for any unfixed
bugs that look similar
* Search the GCC Bugzilla for likely keywords
* And of course try not to cover well-trodden ground in the first place.
I just filed my first Csmith-generated bug report:
Is there anything I could have done that would have made it better?
Anything that's cost-effective for an inexperienced GCC hacker, that
If you know something that's relevant if you replace "GCC" by "LLVM"
in the above text, that's okay too. :)