public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29418] New: [gdb, testsuite/aarch64] FAIL: gdb.ada/O2_float_param.exp: scenario=all: frame
Date: Wed, 27 Jul 2022 14:09:49 +0000 [thread overview]
Message-ID: <bug-29418-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29418
Bug ID: 29418
Summary: [gdb, testsuite/aarch64] FAIL:
gdb.ada/O2_float_param.exp: scenario=all: frame
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With aarch64, I run into:
...
FAIL: gdb.ada/O2_float_param.exp: scenario=all: frame
FAIL: gdb.ada/O2_float_param.exp: scenario=minimal: frame
...
In more detail, we have:
...
(gdb) frame^M
#0 callee.increment (val=99.0, val@entry=9.18340949e-41, msg=...) at
/home/tdevries/gdb/binutils-gdb.git/gdb/testsuite/gdb.ada/O2_float_param/callee.adb:21^M
21 if Val > 200.0 then^M
(gdb) FAIL: gdb.ada/O2_float_param.exp: scenario=all: frame
...
while "val=val@entry=99.0" is expected.
A gcc PR was filed ( https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98148 )
describing in detail why it fails.
The gdb fail should be xfailed for appropriate compiler versions / archs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-27 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 14:09 vries at gcc dot gnu.org [this message]
2022-07-27 14:13 ` [Bug testsuite/29418] " vries at gcc dot gnu.org
2022-09-07 17:22 ` vries at gcc dot gnu.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=bug-29418-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).