public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-5790] libgcc: mark __hardcfr_check_fail as always_inline
@ 2023-11-23 16:32 Jose E. Marchesi
0 siblings, 0 replies; only message in thread
From: Jose E. Marchesi @ 2023-11-23 16:32 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:2eb833534c7e715c276658ecb810715e8718e5c3
commit r14-5790-g2eb833534c7e715c276658ecb810715e8718e5c3
Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Date: Wed Nov 22 15:32:17 2023 +0100
libgcc: mark __hardcfr_check_fail as always_inline
The function __hardcfr_check_fail in hardcfr.c is internal and static
inline. It receives many arguments, which require more than five
registers to be passed in bpf-none-unknown targets. BPF is limited to
that number of registers to pass arguments, and therefore libgcc fails
to build in that target. This patch marks the function with the
always_inline attribute, fixing the bpf build.
Tested in bpf-unknown-none target and x86_64-linux-gnu host.
libgcc/ChangeLog:
* hardcfr.c (__hardcfr_check_fail): Mark as always_inline.
Diff:
---
libgcc/hardcfr.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/libgcc/hardcfr.c b/libgcc/hardcfr.c
index 25ff06742cb..376a36202c8 100644
--- a/libgcc/hardcfr.c
+++ b/libgcc/hardcfr.c
@@ -206,6 +206,10 @@ __hardcfr_debug_cfg (size_t const blocks,
enabled, it also forces __hardcfr_debug_cfg (above) to be compiled into an
out-of-line function, that could be called from a debugger.
*/
+
+#ifdef __BPF__
+__attribute__((__always_inline__))
+#endif
static inline void
__hardcfr_check_fail (size_t const blocks ATTRIBUTE_UNUSED,
vword const *const visited ATTRIBUTE_UNUSED,
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-11-23 16:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-23 16:32 [gcc r14-5790] libgcc: mark __hardcfr_check_fail as always_inline Jose E. Marchesi
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).