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 debug/101283] Several tests fail on Darwin with -gctf/gbtf
Date: Fri, 02 Jul 2021 14:50:38 +0000 [thread overview]
Message-ID: <bug-101283-4-BH5frrhShd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101283-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101283
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:
https://gcc.gnu.org/g:eb817f27e82769aef545d580a0c47a3aa50d1ec4
commit r12-1982-geb817f27e82769aef545d580a0c47a3aa50d1ec4
Author: Iain Sandoe <iain@sandoe.co.uk>
Date: Fri Jul 2 09:44:59 2021 +0100
Darwin, BTF: Provide a suitable section name for BTF [PR101283].
In a similar manner to r12-1960-gcc8453012f75d, this provides a
placeholder section name for BTF data. This change groups BTF
and CTF debug formats in the same segment, but keeps them in
separate sections.
As per the CTF section designation, this should be agreed or
amended to an agreed form before GCC 12 ships.
Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
PR debug/101283 - Several tests fail on Darwin with -gctf/gbtf
PR debug/101283
gcc/ChangeLog:
* config/darwin.h (CTF_INFO_SECTION_NAME): Update the
segment to include BTF.
(BTF_INFO_SECTION_NAME): New.
next prev parent reply other threads:[~2021-07-02 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 11:42 [Bug debug/101283] New: Severaal test fail on Darwin with -gctf dominiq at lps dot ens.fr
2021-07-01 15:56 ` [Bug debug/101283] Several tests " cvs-commit at gcc dot gnu.org
2021-07-01 16:22 ` ibhagatgnu at gmail dot com
2021-07-01 16:32 ` iains at gcc dot gnu.org
2021-07-01 16:46 ` dominiq at lps dot ens.fr
2021-07-02 6:16 ` [Bug debug/101283] Several tests fail on Darwin with -gctf/gbtf rguenth at gcc dot gnu.org
2021-07-02 9:01 ` iains at gcc dot gnu.org
2021-07-02 14:50 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-02 14:50 ` cvs-commit at gcc dot gnu.org
2021-07-02 14:55 ` iains at gcc dot gnu.org
2021-07-02 15:13 ` iains at gcc dot gnu.org
2021-07-05 15:27 ` ibhagatgnu at gmail dot com
2021-07-05 20:42 ` iains at gcc dot gnu.org
2021-07-05 21:20 ` ibhagatgnu at gmail dot com
2021-07-06 0:47 ` cvs-commit at gcc dot gnu.org
2021-07-06 1:28 ` ibhagatgnu at gmail dot com
2021-07-06 21:08 ` cvs-commit at gcc dot gnu.org
2021-07-06 23:05 ` cvs-commit at gcc dot gnu.org
2021-07-06 23:14 ` cvs-commit at gcc dot gnu.org
2021-07-06 23:20 ` ibhagatgnu at gmail dot com
2021-07-09 1:51 ` dje at gcc dot gnu.org
2021-09-27 19:05 ` ibhagatgnu at gmail dot com
2021-09-27 19:09 ` iains at gcc dot gnu.org
2021-09-29 18:08 ` ibhagat 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-101283-4-BH5frrhShd@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).