Re: bison with gcc bounds checking

[Paul Eggert]

ashes <address@hidden> writes:

> bounds checking is an auditing patch for gcc. I've tried to build
> bison-1.875 and 1.875c with -fbound-checking. The build is fine. The
> problem is the 7 new errors from the testsuite. Maybe you guys can
> offer some help with this.
> ...
> /usr/include/stdlib.h: In function `double strtod(const char*, char**)':
> /usr/include/stdlib.h:310: error: reinterpret_cast from `const char* 
>    __restrict*' to `void*' casts away const (or volatile)

>From a quick look at the diagnostics it appears to me that your C++
compiler doesn't like your standard headers.  That is, the problem
doesn't appear to be Bison-related at all.

Did you try building Bison without -fbound-checking?

Can you give a small example of a C++ program that elicits the above
diagnostic, and explain why the Bison-generated C++ parser has the
same problem?