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 target/114431] bpf: GCC generates unverifiable code for systemd restrict_fs_bpf Date: Tue, 26 Mar 2024 16:20:38 +0000 [thread overview] Message-ID: <bug-114431-4-rJB3Yuws1n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114431-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114431 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Cupertino Miranda <cupermir@gcc.gnu.org>: https://gcc.gnu.org/g:fa60ac549649655a3f55e69f83d2e97423d3eb5c commit r14-9677-gfa60ac549649655a3f55e69f83d2e97423d3eb5c Author: Cupertino Miranda <cupertino.miranda@oracle.com> Date: Tue Mar 26 11:59:47 2024 +0000 btf: Emit labels in DATASEC bts_offset entries. GCC was defining bts_offset entry to always contain 0. When comparing with clang, the same entry is instead a label to the respective variable or function. The assembler emits relocations for those labels. gcc/ChangeLog: PR target/114431 * btfout.cc (get_name_for_datasec_entry): Add function. (btf_asm_datasec_entry): Print label when possible. gcc/testsuite/ChangeLog: * gcc.dg/debug/btf/btf-datasec-1.c: Correct for new implementation. * gcc.dg/debug/btf/btf-datasec-2.c: Likewise * gcc.dg/debug/btf/btf-pr106773.c: Likewise
next prev parent reply other threads:[~2024-03-26 16:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-22 10:33 [Bug target/114431] New: " jemarch at gcc dot gnu.org 2024-03-24 9:37 ` [Bug target/114431] " jemarch at gcc dot gnu.org 2024-03-24 15:10 ` jemarch at gcc dot gnu.org 2024-03-24 15:10 ` jemarch at gcc dot gnu.org 2024-03-24 15:11 ` jemarch at gcc dot gnu.org 2024-03-26 16:20 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-26 16:47 ` cupertino.miranda at oracle dot com 2024-03-28 18:13 ` pinskia at gcc dot gnu.org 2024-03-28 19:17 ` jemarch at gcc dot gnu.org 2024-04-09 16:01 ` david.faust at oracle dot com
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-114431-4-rJB3Yuws1n@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).