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++/21554] [4.0 Regression] ext/array_allocator/2.cc execution test fails on hppa64-hpux
Date: Fri, 13 May 2005 20:39:00 -0000 [thread overview]
Message-ID: <20050513203931.28007.qmail@sourceware.org> (raw)
In-Reply-To: <20050513192329.21554.jsm28@gcc.gnu.org>
------- Additional Comments From joseph at codesourcery dot com 2005-05-13 20:39 -------
Subject: Re: [4.0 Regression] ext/array_allocator/2.cc
execution test fails on hppa64-hpux
On Fri, 13 May 2005, pcarlini at suse dot de wrote:
> Given our current basic_string implementation (which I'm maintaining) I can
> tell you that this testcase is very brittle: see 19495, that lead to the
> xfail for powerpc, for additional details. Benjamin's changes cannot have
> directly caused the fail and, IMHO, represent a very welcome clean-up.
So this should be treated as a known latent bug, a testcase which fails or
passes at random on targets requiring strict alignment? In which case
there should be an effective-target keyword for strict alignment and the
testcase should be xfailed on all such targets?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21554
next prev parent reply other threads:[~2005-05-13 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 19:23 [Bug libstdc++/21554] New: " jsm28 at gcc dot gnu dot org
2005-05-13 19:27 ` [Bug libstdc++/21554] " jsm28 at gcc dot gnu dot org
2005-05-13 20:16 ` pcarlini at suse dot de
2005-05-13 20:39 ` joseph at codesourcery dot com [this message]
2005-05-13 21:13 ` pcarlini at suse dot de
2005-06-01 8:33 ` [Bug libstdc++/21554] [4.0 Regression] ext/array_allocator/2.cc execution fails ebotcazou at gcc dot gnu dot org
2005-06-01 8:43 ` pcarlini at suse dot de
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=20050513203931.28007.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).