On 17/10/2007, Roberto Bagnara <[EMAIL PROTECTED]> wrote:
> Manuel López-Ibáñez wrote:
> > On 11/10/2007, Roberto Bagnara <[EMAIL PROTECTED]> wrote:
> >> Just to make sure before I submit a bug report: when GCC says that
> >> a certain variable _is_ (as opposed to _may be_) used uninitialized
> >>
Manuel López-Ibáñez wrote:
On 11/10/2007, Roberto Bagnara <[EMAIL PROTECTED]> wrote:
Just to make sure before I submit a bug report: when GCC says that
a certain variable _is_ (as opposed to _may be_) used uninitialized
in this function, it means that it has proved that the variable
is indeed us
On 11/10/2007, Roberto Bagnara <[EMAIL PROTECTED]> wrote:
>
> Just to make sure before I submit a bug report: when GCC says that
> a certain variable _is_ (as opposed to _may be_) used uninitialized
> in this function, it means that it has proved that the variable
> is indeed used uninitialized, ri
On 11/10/2007, Roberto Bagnara <[EMAIL PROTECTED]> wrote:
>
> Just to make sure before I submit a bug report: when GCC says that
> a certain variable _is_ (as opposed to _may be_) used uninitialized
> in this function, it means that it has proved that the variable
> is indeed used uninitialized, ri
Just to make sure before I submit a bug report: when GCC says that
a certain variable _is_ (as opposed to _may be_) used uninitialized
in this function, it means that it has proved that the variable
is indeed used uninitialized, right?
I am asking because I have a testcase where g++ gives this w