public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/113382] FAIL: gcc.dg/debug/btf/btf-bitfields-3.c scan-assembler-times [\t ]0x6000004[\t ]+[^\n]*btt_info 1 Date: Sun, 21 Jan 2024 22:54:12 +0000 [thread overview] Message-ID: <bug-113382-4-THTlbKXsNN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113382-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113382 --- Comment #2 from John David Anglin <danglin at gcc dot gnu.org> --- We have: .word 0x86000004 ; btt_info: kind=6, kflag=1, vlen=4 This seems correct encoding: /* Encoding for struct btf_type.info. */ #define BTF_TYPE_INFO(kind, kflag, vlen) \ ((((kflag) ? 1 : 0 ) << 31) | ((kind) << 24) | ((vlen) & 0xffff)) Problem seems kflag.
next prev parent reply other threads:[~2024-01-21 22:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 19:24 [Bug debug/113382] New: " danglin at gcc dot gnu.org 2024-01-21 22:00 ` [Bug debug/113382] " danglin at gcc dot gnu.org 2024-01-21 22:54 ` danglin at gcc dot gnu.org [this message] 2024-01-22 2:35 ` danglin at gcc dot gnu.org 2024-01-22 15:34 ` danglin at gcc dot gnu.org 2024-01-22 18:09 ` danglin at gcc dot gnu.org 2024-01-22 19:08 ` cvs-commit at gcc dot gnu.org 2024-01-22 19:12 ` danglin 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-113382-4-THTlbKXsNN@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: linkBe 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).