public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/55413] [LTO] hashtable.h:1648 '__bbegin_bkt' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Date: Tue, 20 Nov 2012 14:55:00 -0000	[thread overview]
Message-ID: <bug-55413-4-duAqCDlvCV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55413-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55413

--- Comment #4 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> 2012-11-20 14:54:48 UTC ---
Author: paolo
Date: Tue Nov 20 14:54:36 2012
New Revision: 193664

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193664
Log:
2012-11-20  Paolo Carlini  <paolo.carlini@oracle.com>

    PR libstdc++/55413
    * include/bits/hashtable.h (_Hashtable<>::_M_rehash_aux): Initialize
    __bbegin_bkt and __prev_bkt to avoid uninitialized warnings.
    * testsuite/23_containers/unordered_set/instantiation_neg.cc: Adjust
    dg-error line number.

Modified:
    branches/gcc-4_7-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_7-branch/libstdc++-v3/include/bits/hashtable.h
   
branches/gcc-4_7-branch/libstdc++-v3/testsuite/23_containers/unordered_set/instantiation_neg.cc


  parent reply	other threads:[~2012-11-20 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 14:06 [Bug libstdc++/55413] New: " david.abdurachmanov at gmail dot com
2012-11-20 14:09 ` [Bug libstdc++/55413] " david.abdurachmanov at gmail dot com
2012-11-20 14:16 ` paolo.carlini at oracle dot com
2012-11-20 14:55 ` paolo at gcc dot gnu.org
2012-11-20 14:55 ` paolo at gcc dot gnu.org [this message]
2012-11-20 14:56 ` paolo.carlini at oracle dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55413-4-duAqCDlvCV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).