public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/23667] [4.0/4.1 Regression] tr1/6_containers/unordered/hashtable/23465.cc execution test times out
Date: Fri, 02 Sep 2005 16:12:00 -0000 [thread overview]
Message-ID: <20050902161206.12433.qmail@sourceware.org> (raw)
In-Reply-To: <20050901014342.23667.jsm28@gcc.gnu.org>
------- Additional Comments From joseph at codesourcery dot com 2005-09-02 16:12 -------
Subject: Re: [4.0/4.1 Regression]
tr1/6_containers/unordered/hashtable/23465.cc execution test times out
On Thu, 1 Sep 2005, pcarlini at suse dot de wrote:
> Hi. Can you have a quick look at what is going on outside the testsuite? (as
> usual, just change testsuite_hooks.h to cassert and any VERIFY to assert). For
> reference, on a P4-2400/linux running the test takes around 1/4 of sec, therefore
> I suspect something is going seriously wrong in the compiler... But, if it's just
> a matter of making the testcase a little simpler (on the border of timing out on
> those platforms), not a big deal, just let me know.
Running outside the testsuite, it appears to hang (taking at least 3min)
on hppa64-hp-hpux11.11, whereas by comparison on the same machine but
configured for hppa2.0w-hp-hpux11.11 (32-bit rather than 64-bit) it takes
19s user time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23667
next prev parent reply other threads:[~2005-09-02 16:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 1:43 [Bug libstdc++/23667] New: " jsm28 at gcc dot gnu dot org
2005-09-01 8:32 ` [Bug libstdc++/23667] " pcarlini at suse dot de
2005-09-01 8:44 ` pcarlini at suse dot de
2005-09-02 16:12 ` joseph at codesourcery dot com [this message]
2005-09-02 16:17 ` pcarlini at suse dot de
2005-09-02 16:38 ` pcarlini at suse dot de
2005-09-02 19:09 ` pcarlini at suse dot de
2005-09-02 19:18 ` [Bug c++/23667] " pinskia at gcc dot gnu dot org
2005-09-02 19:23 ` [Bug libstdc++/23667] " pcarlini at suse dot de
2005-09-02 19:25 ` [Bug c++/23667] " pcarlini at suse dot de
2005-09-02 19:31 ` pinskia at gcc dot gnu dot org
2005-09-02 21:29 ` pcarlini at suse dot de
2005-09-03 1:16 ` pcarlini at suse dot de
2005-09-03 1:31 ` pcarlini at suse dot de
2005-09-03 18:52 ` mmitchel at gcc dot gnu dot org
2005-09-03 19:04 ` pinskia at gcc dot gnu dot org
2005-09-03 20:08 ` mark at codesourcery dot com
2005-09-03 23:06 ` pcarlini at suse dot de
2005-09-04 3:08 ` mark at codesourcery dot com
2005-09-04 14:10 ` pcarlini at suse dot de
2005-09-05 16:12 ` cvs-commit at gcc dot gnu dot org
2005-09-05 16:13 ` cvs-commit at gcc dot gnu dot org
2005-09-05 16:15 ` mmitchel at gcc dot gnu dot org
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=20050902161206.12433.qmail@sourceware.org \
--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).