public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jose.marchesi at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104656] [12 Regression] trunk 20220222 ftbfs for bpf
Date: Wed, 23 Feb 2022 13:15:32 +0000 [thread overview]
Message-ID: <bug-104656-4-IfuKQVo04w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104656-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104656
Jose E. Marchesi <jose.marchesi at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jose.marchesi at oracle dot com
--- Comment #5 from Jose E. Marchesi <jose.marchesi at oracle dot com> ---
Yes that would require changing the kernel ABI. Also, there is the kernel
verifier to deal with: stack accesses are tracked at load-time and they should
be done using certain registers and following certain rules.
For the time being, --disabling-gcov when building for BPF seems like a
reasonable thing to do. Will write and send a patch in that effect.
next prev parent reply other threads:[~2022-02-23 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 8:55 [Bug target/104656] New: " doko at debian dot org
2022-02-23 10:38 ` [Bug gcov-profile/104656] " pinskia at gcc dot gnu.org
2022-02-23 10:41 ` [Bug target/104656] " rguenth at gcc dot gnu.org
2022-02-23 11:04 ` doko at debian dot org
2022-02-23 11:09 ` jakub at gcc dot gnu.org
2022-02-23 11:16 ` pinskia at gcc dot gnu.org
2022-02-23 13:15 ` jose.marchesi at oracle dot com [this message]
2022-02-24 15:44 ` cvs-commit at gcc dot gnu.org
2022-03-09 13:02 ` rguenth 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-104656-4-IfuKQVo04w@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).