public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/114642] New: new test case gcc.dg/debug/btf/btf-datasec-3.c from r14-6195-gb8cf266f4ca4ff fails for 32 bits
Date: Mon, 08 Apr 2024 15:38:15 +0000 [thread overview]
Message-ID: <bug-114642-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114642
Bug ID: 114642
Summary: new test case gcc.dg/debug/btf/btf-datasec-3.c from
r14-6195-gb8cf266f4ca4ff fails for 32 bits
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:b8cf266f4ca4ff89704b190c827abf9ea7e7b5bf, r14-6195-gb8cf266f4ca4ff
I only see this failing on 32 bit.
make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
btf.exp=gcc.dg/debug/btf/btf-datasec-3.c"
FAIL: gcc.dg/debug/btf/btf-datasec-3.c scan-assembler-times bts_type 3
FAIL: gcc.dg/debug/btf/btf-datasec-3.c scan-assembler-times bts_type:
\\(BTF_KIND_VAR 'test_data2'\\) 1
FAIL: gcc.dg/debug/btf/btf-datasec-3.c scan-assembler-times bts_type:
\\(BTF_KIND_VAR 'test_bss2'\\) 1
# of expected passes 2
# of unexpected failures 3
Author: David Faust <david.faust@oracle.com>
Date: Mon Dec 4 14:08:03 2023 -0800
btf: avoid wrong DATASEC entries for extern vars [PR112849]
* gcc.dg/debug/btf/btf-datasec-3.c: New test.
next reply other threads:[~2024-04-08 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 15:38 seurer at gcc dot gnu.org [this message]
2024-04-09 0:04 ` [Bug testsuite/114642] " pinskia at gcc dot gnu.org
2024-04-09 1:58 ` linkw at gcc dot gnu.org
2024-04-09 2:03 ` pinskia at gcc dot gnu.org
2024-04-09 18:12 ` cvs-commit 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-114642-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).