From: Li Guanglei <guanglei@cn.ibm.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: gcc stop compiling a large stap generated c file
Date: Wed, 11 Oct 2006 09:16:00 -0000 [thread overview]
Message-ID: <452CB6BF.5020501@cn.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
Hi,
I tried: stap -e 'probe addevent.* {}' -bM -v
on ppc64/RHEL4u4/gcc-3.4.6, and got a lot of errors of "operand out
of range".
the generated c file is really big:
root:/tmp/stapRl4mJy> ll -h
total 7.5M
-rw-r--r-- 1 root root 128 Oct 9 17:53 Makefile
-rw-r--r-- 1 root root 6.3M Oct 9 17:53 stap_11644.c
-rw-r--r-- 1 root root 714K Oct 9 17:53 stap-symbols.h
-rw-r--r-- 1 root root 527K Oct 9 17:53 symbols.sorted
I searched gcc bugzilla, and found someone reported the same kind
of error on gcc 4.1:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28904
I think it's common for SystemTap to generate a large c file if the
number of probes and functions turned on is big. I tried on i386 and
it doesn't have this error. Does anyone know if there is any
alternative to avoid such error for ppc64?
thanks.
- Guanglei
[-- Attachment #2: gcc.err --]
[-- Type: text/plain, Size: 1977 bytes --]
Running grep " [tT] " /proc/kallsyms | sort -k 1,8 -s -o /tmp/stapRl4mJy/symbols.sorted
Pass 3: translated to C into "/tmp/stapRl4mJy/stap_11644.c" in 1180usr/200sys/1614real ms.
Running make -C "/lib/modules/2.6.17.9/build" M="/tmp/stapRl4mJy" modules V=1
make: Entering directory `/usr/src/linux-2.6.17.9'
mkdir -p /tmp/stapRl4mJy/.tmp_versions
rm -f /tmp/stapRl4mJy/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/stapRl4mJy
gcc -m64 -Wp,-MD,/tmp/stapRl4mJy/.stap_11644.o.d -nostdinc -isystem /usr/lib/gcc/ppc64-redhat-linux/3.4.6/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Os -fomit-frame-pointer -g -msoft-float -pipe -mminimal-toc -mtraceback=none -mcall-aixdesc -mtune=power4 -mno-altivec -funit-at-a-time -mstring -Wa,-maltivec -Wdeclaration-after-statement -freorder-blocks -Wno-unused -Werror -I"/usr/local/share/systemtap/runtime" -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(stap_11644)" -D"KBUILD_MODNAME=KBUILD_STR(stap_11644)" -c -o /tmp/stapRl4mJy/.tmp_stap_11644.o /tmp/stapRl4mJy/stap_11644.c
{standard input}: Assembler messages:
{standard input}:642879: Error: operand out of range (0x0000000000008000 is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:642895: Error: operand out of range (0x0000000000008008 is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:643196: Error: operand out of range (0x0000000000008018 is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:643197: Error: operand out of range (0x0000000000008010 is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:643284: Error: operand out of range (0x0000000000008020 is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:643300: Error: operand out of range (0x0000000000008028 is not between 0xffffffffffff8000 and 0x0000000000007fff)
...
next reply other threads:[~2006-10-11 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 9:16 Li Guanglei [this message]
2006-10-11 13:45 ` Frank Ch. Eigler
2006-10-11 14:34 ` Vara Prasad
2006-10-13 22:56 ` Alan Modra
2006-10-11 14:45 ` Mike Mason
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=452CB6BF.5020501@cn.ibm.com \
--to=guanglei@cn.ibm.com \
--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).