public inbox for
 help / color / mirror / Atom feed
From: "agentzh at gmail dot com" <>
Subject: [Bug runtime/27301] New: Aarch64 ko compilation failures when CONFIG_COMPAT is defined
Date: Mon, 01 Feb 2021 01:31:00 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 27301
           Summary: Aarch64 ko compilation failures when CONFIG_COMPAT is
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: agentzh at gmail dot com
  Target Milestone: ---

When CONFIG_COMPAT is defined in the kernel's config, stap fails to compile its
runtime on Fedora 32 (kernel 5.10):

$ /opt/stap/bin/stap -e 'probe process.function("main") {
println(register("x0")) }' -c ./a.out
WARNING: cannot find module /home/agentzh/git/ debuginfo: No
DWARF information found [man warning::debuginfo]
In file included from
                 from /opt/stap/share/systemtap/runtime/linux/../regs.c:20,
                 from /opt/stap/share/systemtap/runtime/linux/runtime.h:251,
                 from /opt/stap/share/systemtap/runtime/runtime.h:26,
/opt/stap/share/systemtap/runtime/compatdefs.h: In function
/opt/stap/share/systemtap/runtime/compatdefs.h:38:2: error: #error architecture
not supported, no TIF_32BIT flag?
   38 | #error architecture not supported, no TIF_32BIT flag?
      |  ^~~~~
/opt/stap/share/systemtap/runtime/compatdefs.h:40:1: error: no return statement
in function returning non-void [-Werror=return-type]
   40 | }
      | ^
cc1: all warnings being treated as errors
make[1]: *** [scripts/
/tmp/stapLY6U32/stap_9b24fb2c80d42c5c58d165f9c20c403e_6889_src.o] Error 1
make: *** [Makefile:1806: /tmp/stapLY6U32] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed.  [man error::pass4]

That part of runtime code does not handle aarch64 at all. A fix is easy.

A patch is under way.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-02-01  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  1:31 agentzh at gmail dot com [this message]
2021-02-01  1:32 ` [Bug runtime/27301] " agentzh at gmail dot com
2021-02-01  4:20 ` agentzh at gmail 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).