public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "xuchunmei at linux dot alibaba.com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25994] inproper order of PATH set cause wrong unexpected gcc used
Date: Sat, 16 May 2020 02:25:14 +0000	[thread overview]
Message-ID: <bug-25994-6586-tQGQ3JLIEl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25994-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25994

--- Comment #2 from xuchunmei <xuchunmei at linux dot alibaba.com> ---
(In reply to Frank Ch. Eigler from comment #1)
> The problem is that for systemtap to build kernel modules compatible with
> the system kernel, it must use the same compiler.  Jumping between major
> versions can create incompatible modules, whether enforced by symbol
> versioning type metadata, or undetected inconsistencies in kernel struct
> declarations.
> 
> Any idea where those -fpatchable-function-entry=2 cflags are coming from? 
> Maybe we can nuke those from within stap more properly.

yes, My kernel is build with devtoolset-9-gcc, and systemtap is also build with
devtoolset-9, when I use systemtap I want to use gcc which is
/opt/rh/devtoolset-9/root/usr/bin/gcc not /usr/bin/gcc.

the "-fpatchable-function-entry=2" is from arch/arm64/Makefile:

ifeq ($(CONFIG_DYNAMIC_FTRACE_WITH_REGS),y)
  KBUILD_CPPFLAGS += -DCC_USING_PATCHABLE_FUNCTION_ENTRY
  CC_FLAGS_FTRACE := -fpatchable-function-entry=2
endif

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

  parent reply	other threads:[~2020-05-16  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  6:50 [Bug translator/25994] New: " xuchunmei at linux dot alibaba.com
2020-05-15 12:40 ` [Bug translator/25994] " fche at redhat dot com
2020-05-16  2:25 ` xuchunmei at linux dot alibaba.com [this message]
2020-05-16  3:34 ` xuchunmei at linux dot alibaba.com
2020-05-16  9:51 ` fche at redhat dot com
2020-05-16 10:44 ` xuchunmei at linux dot alibaba.com
2020-07-03  3:01 ` xuchunmei at linux dot alibaba.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-25994-6586-tQGQ3JLIEl@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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).