public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/101269] [12 Regression] new test case gcc.dg/debug/btf/btf-datasec-1.c fails with its introduction in r12-1852
Date: Fri, 09 Jul 2021 16:12:35 +0000 [thread overview]
Message-ID: <bug-101269-4-4SaV69qbVt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101269-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101269
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Indu Bhagat <ibhagat@gcc.gnu.org>:
https://gcc.gnu.org/g:37e65643d3e32d33bb6c9d15c678a627d1682626
commit r12-2223-g37e65643d3e32d33bb6c9d15c678a627d1682626
Author: Indu Bhagat <indu.bhagat@oracle.com>
Date: Fri Jul 9 09:03:08 2021 -0700
testsuite/101269: fix testcase when used with -m32
PR testsuite/101269 - new test case gcc.dg/debug/btf/btf-datasec-1.c
fails with its introduction in r12-1852
BTF datasec records for .rodata/.data are expected for now for all targets.
For powerpc based targets, use -msdata=none when ilp32 is enabled.
2021-07-09 Indu Bhagat <indu.bhagat@oracle.com>
gcc/testsuite/ChangeLog:
PR testsuite/101269
* gcc.dg/debug/btf/btf-datasec-1.c: Force -msdata=none with ilp32
for
powerpc based targets.
next prev parent reply other threads:[~2021-07-09 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 13:51 [Bug testsuite/101269] New: " seurer at gcc dot gnu.org
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 [this message]
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-4SaV69qbVt@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).