Re: [csmith-dev] Csmith 2.1 (Re: Csmith TODO list)

[John Regehr <regehr@cs.utah.edu>]

Cool.  Then Eric and I will push out the 2.1 release.  There's a lot of 
good stuff added since 2.0.

John



On 11/14/2011 12:26 PM, Xuejun Yang wrote:
> I’ll try to fix them this week. Thanks for reporting and tracking them, Pascal.
>
> -Xuejun
>
> *From:*csmith-dev-bounces@flux.utah.edu
> [mailto:csmith-dev-bounces@flux.utah.edu] *On Behalf Of *Pascal Cuoq
> *Sent:* Saturday, November 12, 2011 12:22 PM
> *To:* John Regehr
> *Cc:* csmith-dev@flux.utah.edu
> *Subject:* Re: [csmith-dev] Csmith 2.1 (Re: Csmith TODO list)
>
> On Sat, Nov 12, 2011 at 9:06 PM, John Regehr <regehr@cs.utah.edu
> <mailto:regehr@cs.utah.edu>> wrote:
>
>     Ok, sounds like the main thing is we'd like to have the queue of real
>     bugs (from Pascal) be empty.
>
> As far as I remember, the bugs that remain open at this point are:
>
> - auto-increment of bitfield may cause overflow in signed int arithmetics:
>
> http://www.flux.utah.edu/listarchives/csmith-dev/msg00314.html
>
> - accessing uninitialized members of unions with option --bitfields set
> (common):
>
> http://www.flux.utah.edu/listarchives/csmith-bugs/msg00103.html
>
> - accessing uninitialized members of unions with option --no-bitfields (rare):
>
> http://www.flux.utah.edu/listarchives/csmith-bugs/msg00110.html
>
> Pascal