This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [rant?] g++ bug (missing uninitialized warning), bug reporting, bug searching


Hello,

On Fri, 2012-11-09 at 12:18 -0800, Bruno Nery wrote:
> Howdy,
> 
> The following piece of code:
> 
> === snip ===
> #include <iostream>
> 
> struct warnme
> {
>     bool member_;
>     warnme(bool member) : member_(member_) {}
> };
> 
> int main()
> {
>     warnme wm(true);
>     std::cout << wm.member_ << std::endl;
>     return 0;
> }
> === end snip ===
> 
> when compiled with g++ 4.7, gives me no warnings - even with
> -Wuninitialized (clang++ 3.1 is fine, by the way). I then decided to
> report a bug, but:
> 
> - I need to login to report a bug, and I have to create an account. Is
> this a way to reduce the number of bugs GCC gets?

This issue has been raised just recently on the gcc-help mailing list.
See the thread:
http://gcc.gnu.org/ml/gcc-help/2012-10/threads.html#00061

> - I searched for uninitialized and got 156 bugs. How easy would it be
> for one to check if a bug is a duplicate? Shouldn't we have some kind
> of code search for bug-related snippets?

I've just searched for "uninitialized missing" and got 22 bugs, some of
them seem to look related to yours, although I haven't checked/compared
the details.  In the worst case you can just file the bug and it will be
marked as duplicate eventually (if it is one).

Cheers,
Oleg


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]