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/101269] New: new test case gcc.dg/debug/btf/btf-datasec-1.c fails with its introduction in r12-1852
Date: Wed, 30 Jun 2021 13:51:42 +0000 [thread overview]
Message-ID: <bug-101269-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101269
Bug ID: 101269
Summary: new test case gcc.dg/debug/btf/btf-datasec-1.c fails
with its introduction in r12-1852
Product: gcc
Version: 12.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:c1f76af469388d3df815c82de566387da5ae000f, r12-1852
FAIL: gcc.dg/debug/btf/btf-datasec-1.c scan-assembler-times 0[\t
]+[^\n]*bts_offset 7
FAIL: gcc.dg/debug/btf/btf-datasec-1.c scan-assembler-times 0xf000003[\t
]+[^\n]*btt_info 2
FAIL: gcc.dg/debug/btf/btf-datasec-1.c scan-assembler-times ascii ".data.0"[\t
]+[^\n]*btf_aux_string 1
FAIL: gcc.dg/debug/btf/btf-datasec-1.c scan-assembler-times ascii
".rodata.0"[\t ]+[^\n]*btf_aux_string 1
It looks like the failing ones are compiled for 32 bits. The 64 bits ones work
fine.
commit c1f76af469388d3df815c82de566387da5ae000f
Author: Indu Bhagat <indu.bhagat@oracle.com>
Date: Thu May 20 11:19:04 2021 -0700
CTF/BTF testsuites
This commit adds a new testsuite for the CTF debug format.
next reply other threads:[~2021-06-30 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 13:51 seurer at gcc dot gnu.org [this message]
2021-06-30 19:22 ` [Bug testsuite/101269] " ibhagatgnu at gmail dot com
2021-07-01 7:15 ` [Bug testsuite/101269] [12 Regression] " rguenth at gcc dot gnu.org
2021-07-09 16:12 ` cvs-commit at gcc dot gnu.org
2021-09-27 18:48 ` ibhagatgnu at gmail dot com
2021-09-27 19:16 ` seurer 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-101269-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).