public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.faust at oracle dot com" <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, 09 Apr 2024 16:01:34 +0000 [thread overview]
Message-ID: <bug-114431-4-YQC3i9AvtL@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
David Faust <david.faust at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david.faust at oracle dot com
--- Comment #7 from David Faust <david.faust at oracle dot com> ---
Patch above had some fallout for non-BPF targets. I pushed the below to fix
that. The behavior for BPF is unchanged.
https://gcc.gnu.org/g:8075477f81ae8d0abf64b80dfbd179151f91b417
commit r14-9876-g8075477f81ae8d0abf64b80dfbd179151f91b417
Author: David Faust <david.faust@oracle.com>
Date: Mon Apr 8 11:10:41 2024 -0700
btf: emit symbol refs in DATASEC entries only for BPF [PR114608]
prev parent reply other threads:[~2024-04-09 16:01 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
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 [this message]
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-YQC3i9AvtL@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).