Bug 29418 - [gdb, testsuite/aarch64] FAIL: gdb.ada/O2_float_param.exp: scenario=all: frame
Summary: [gdb, testsuite/aarch64] FAIL: gdb.ada/O2_float_param.exp: scenario=all: frame
Status: RESOLVED FIXED
Alias: None
Product: gdb
Classification: Unclassified
Component: testsuite (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: 13.1
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-27 14:09 UTC by Tom de Vries
Modified: 2022-09-07 17:22 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom de Vries 2022-07-27 14:09:49 UTC
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.
Comment 1 Tom de Vries 2022-07-27 14:13:26 UTC
(In reply to Tom de Vries from comment #0)
> The gdb fail should be xfailed for appropriate compiler versions / archs.

Or, alternatively, discarding the incorrect DW_AT_GNU_call_site_value in gdb.