public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/63332] New: problem with VERIFY in ext/random/k_distribution/operators/serialize.cc execution test
Date: Mon, 22 Sep 2014 13:35:00 -0000 [thread overview]
Message-ID: <bug-63332-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63332
Bug ID: 63332
Summary: problem with VERIFY in
ext/random/k_distribution/operators/serialize.cc
execution test
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: richard at netbsd dot org
Created attachment 33531
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33531&action=edit
testsuite module updated with couts showing issue is with VERIFY
Working with gcc49 on SunOS 5.11 i386 (Omnios) and pkgsrc (32-bit trunk)
I came across the following failure:
FAIL: ext/random/k_distribution/operators/serialize.cc execution test
scratching my head a bit, I added some outputs and found that the problem is
with VERIFY and not with the functions being tested.
here is my output with the attached (modified) serialize.cc:
$ ./a.out
u: 2.00000000000000000e+00 1.50000000000000000e+00 3.00000000000000000e+00
2.00000000000000000e+00 5.00000000000000000e-01 0.00000000000000000e+00
1.00000000000000000e+00 1 -1.08681804426135680e+00 3.00000000000000000e+00
5.00000000000000000e-01 0.00000000000000000e+00 1.00000000000000000e+00 1
1.89131873404367808e-01
v: 2.00000000000000000e+00 1.50000000000000000e+00 3.00000000000000000e+00
2.00000000000000000e+00 5.00000000000000000e-01 0.00000000000000000e+00
1.00000000000000000e+00 1 -1.08681804426135680e+00 3.00000000000000000e+00
5.00000000000000000e-01 0.00000000000000000e+00 1.00000000000000000e+00 1
1.89131873404367808e-01
Assertion failed: u == v, file serialize.cc, line 48, function test01
Abort (core dumped)
next reply other threads:[~2014-09-22 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 13:35 richard at netbsd dot org [this message]
2014-09-22 13:37 ` [Bug testsuite/63332] " richard at netbsd dot org
2014-09-25 10:06 ` redi at gcc dot gnu.org
2014-09-25 10:14 ` [Bug libstdc++/63332] " redi at gcc dot gnu.org
2014-09-25 15:30 ` richard at netbsd dot org
2014-09-25 16:04 ` richard at netbsd dot org
2014-09-25 16:08 ` richard at netbsd dot org
2014-09-25 16:18 ` redi at gcc dot gnu.org
2014-11-16 7:05 ` richard at netbsd dot org
2014-11-16 14:35 ` redi at gcc dot gnu.org
2020-10-08 14:05 ` redi at gcc dot gnu.org
2020-10-11 11:04 ` ro at CeBiTec dot Uni-Bielefeld.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=bug-63332-4@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).