From: Florent DEFAY <spira.inhabitant@gmail.com>
To: ganesh gopalasubramanian <gganeshgcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: error while x-compiling libgcc2.c
Date: Tue, 31 Mar 2009 07:29:00 -0000 [thread overview]
Message-ID: <8502af3c0903310029p79cb9e0dr92f656b4fc91bf76@mail.gmail.com> (raw)
In-Reply-To: <7238340b0903310000i6034b1d3r240e1a510ff01af3@mail.gmail.com>
> We tried building the libraries using the make script and it ended up
> with the error. For debugging we compiled the file (libgcc2.c) in the
> path and it went on fine. Any idea about this situation?
Do you mean 'make' ended up with error and compiling libgcc2.c alone
comes to no problem ?
How do you perform debugging ?
The easiest way I know is
1- make
2- select the last compilation (the one which provokes error)
3-run gdb --arg [last compilation]
Here is a cancrete example:
/home/guest1/gcc/build_target/./gcc/xgcc
-B/home/guest1/gcc/build_target/./gcc/
-B/home/guest1/target/target/bin/ -B/home/guest1/target/target/lib/
-isystem /home/guest1/target/target/include -isystem
/home/guest1/target/target/sys-include -O2 -g -g -O2 -O2 -O2 -g -g
-O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-Dinhibit_libc -I. -I. -I../.././gcc -I../../../gcc-4.3.3/libgcc
-I../../../gcc-4.3.3/libgcc/. -I../../../gcc-4.3.3/libgcc/../gcc
-I../../../gcc-4.3.3/libgcc/../include -o _muldi3.o -MT _muldi3.o
-MD -MP -MF _muldi3.dep -DL_muldi3 -c
../../../gcc-4.3.3/libgcc/../gcc/libgcc2.c \
xgcc: Internal error: Segmentation fault (program cc1)
Please submit a full bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [_muldi3.o] Error 1
...
prompt$ gdb --args /home/guest1/gcc/build_target/./gcc/xgcc
-B/home/guest1/gcc/build_target/./gcc/
-B/home/guest1/target/target/bin/ -B/home/guest1/target/target/lib/
-isystem /home/guest1/target/target/include -isystem
/home/guest1/target/target/sys-include -O2 -g -g -O2 -O2 -O2 -g -g
-O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED
-Dinhibit_libc -I. -I. -I../.././gcc -I../../../gcc-4.3.3/libgcc
-I../../../gcc-4.3.3/libgcc/. -I../../../gcc-4.3.3/libgcc/../gcc
-I../../../gcc-4.3.3/libgcc/../include -o _muldi3.o -MT _muldi3.o
-MD -MP -MF _muldi3.dep -DL_muldi3 -c
../../../gcc-4.3.3/libgcc/../gcc/libgcc2.c
Here is the complete list of patterns I implemented and are sufficient
(in my case) to compile libgcc:
movqi,hi,si,di
exetendqihi2,hisi2,sidi2
zero_extendqihi2,hisi2,sidi2
add,sub,neg in qi,hi,si,di modes
mulhi,si
umulqihi3,hisi3,sidi3
divmodqi4,hi4
jump
indirect_jump
cmphi
all branch
all reverse branch
prologue,epilogue,call,call_value,nop.
Regards.
Florent
next prev parent reply other threads:[~2009-03-31 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 6:19 ganesh gopalasubramanian
2009-03-31 6:51 ` Florent DEFAY
2009-03-31 7:01 ` ganesh gopalasubramanian
2009-03-31 7:29 ` Florent DEFAY [this message]
2009-03-31 7:47 ` Florent DEFAY
2009-03-31 14:23 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2009-03-25 15:33 Florent DEFAY
2009-03-25 18:50 ` Georg-Johann Lay
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=8502af3c0903310029p79cb9e0dr92f656b4fc91bf76@mail.gmail.com \
--to=spira.inhabitant@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gganeshgcc@gmail.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).