public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/64694] [5 Regression] FAIL: 23_containers/unordered_set/insert/hash_policy.cc
Date: Tue, 20 Jan 2015 21:40:00 -0000	[thread overview]
Message-ID: <bug-64694-4-1d0gjkYYbd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64694-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64694

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at ucw dot cz

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
r219076 has

1674        return target_cfa - current->cfa + target->args_size;
(gdb) bt
#0  uw_install_context_1 (current=current@entry=0xffffcc00, 
    target=target@entry=0xffffcce0)
    at ../../../../../../gcc/libgcc/unwind-dw2.c:1674
#1  0xf757fd4e in _Unwind_RaiseException (exc=<optimized out>)
    at ../../../../../../gcc/libgcc/unwind.inc:135
#2  0x00402bb6 in std::_Hashtable<int, int,
__gnu_cxx::throw_allocator_limit<int>, std::__detail::_Identity,
std::equal_to<int>, std::hash<int>, std::__detail::_Mod_range_hashing,
std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy,
std::__detail::_Hashtable_traits<false, true, true> >::_M_rehash
    (this=this@entry=0xffffd0c0, __n=<optimized out>, __state=@0xffffd0ac: 199)
    at
/export/gnu/import/git/gcc-regression/master/219077/bld/x86_64-unknown-linux-gnu/x32/libstdc++-v3/include/bits/hashtable.h:1953
#3  0x00403533 in __rehash_policy (__pol=..., this=0xffffd0c0)
    at
/export/gnu/import/git/gcc-regression/master/219077/bld/x86_64-unknown-linux-gnu/x32/libstdc++-v3/include/bits/hashtable.h:1291
#4  max_load_factor (__z=0.5, this=0xffffd0c0)
    at
/export/gnu/import/git/gcc-regression/master/219077/bld/x86_64-unknown-linux-gnu/x32/libstdc++-v3/include/bits/hashtable_policy.h:953
#5  max_load_factor (__z=0.5, this=0xffffd0c0)
    at
/export/gnu/import/git/gcc-regression/master/219077/bld/x86_64-unknown-linux-gnu/x32/libstdc++-v3/include/bits/unordered_set.h:678
#6  test01 ()
    at
/export/gnu/import/git/gcc-regression/gcc/libstdc++-v3/testsuite/23_conta---Type
<return> to continue, or q <return> to quit---
iners/unordered_set/max_load_factor/robustness.cc:48
#7  0x00400f78 in main ()
    at
/export/gnu/import/git/gcc-regression/gcc/libstdc++-v3/testsuite/23_containers/unordered_set/max_load_factor/robustness.cc:75
(gdb) 

return target_cfa - current->cfa + target->args_size;

returns 0xd0.  But it should be 0x30.


  parent reply	other threads:[~2015-01-20 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 16:59 [Bug ipa/64694] New: " hjl.tools at gmail dot com
2015-01-20 20:51 ` [Bug ipa/64694] " hjl.tools at gmail dot com
2015-01-20 21:40 ` hjl.tools at gmail dot com [this message]
2015-01-20 23:40 ` hjl.tools at gmail dot com
2015-01-22 18:01 ` hjl.tools at gmail dot com
2015-01-22 18:44 ` hubicka at ucw dot cz
2015-01-22 18:52 ` hubicka at ucw dot cz
2015-01-22 19:32 ` hjl.tools at gmail dot com
2015-01-22 23:15 ` hjl.tools at gmail dot com
2015-01-23  0:35 ` hubicka at gcc dot gnu.org
2015-01-23  1:24 ` hjl.tools at gmail 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-64694-4-1d0gjkYYbd@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).