From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2910] TOC overflow- stap failed to build testsuite/systemtap.syscall/sys.stp on ppc64
Date: Wed, 12 Jul 2006 23:21:00 -0000 [thread overview]
Message-ID: <20060712232132.21302.qmail@sourceware.org> (raw)
In-Reply-To: <20060712193502.2910.hien@us.ibm.com>
------- Additional Comments From fche at redhat dot com 2006-07-12 23:21 -------
hien supplied this corresponding gcc command line:
gcc -m64 -Wp,-MD,/tmp/stap8c45vL/.stap_6224.o.d -nostdinc -iwithprefix
include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common -Os -g -Wdeclaration-after-statement
-msoft-float -pipe -mminimal-toc -mtraceback=none -mcall-aixdesc
-mtune=power4 -fno-unit-at-a-time -freorder-blocks -Wno-unused -Werror
-I"/root/stap_testing_200607102240/src/runtime" -DMODULE
-DKBUILD_BASENAME=stap_6224 -DKBUILD_MODNAME=stap_6224 -c -o
/tmp/stap8c45vL/.tmp_stap_6224.o /tmp/stap8c45vL/stap_6224.c
It indicates that the -mfull-toc and -mtoc that appear in the attached
verbose-asm source file do not come directly from the kernel makefiles.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2910
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-07-12 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 19:35 [Bug translator/2910] New: " hien at us dot ibm dot com
2006-07-12 19:54 ` [Bug translator/2910] " fche at redhat dot com
2006-07-12 21:15 ` hien at us dot ibm dot com
2006-07-12 23:21 ` fche at redhat dot com [this message]
2006-10-12 13:17 ` guanglei at cn dot ibm dot com
2006-10-12 15:31 ` fche at redhat dot com
2006-11-01 22:03 ` fche at redhat 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:
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=20060712232132.21302.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).