Thanks for the below details. I am configuring the gcc using raja.saleru@raja ~/obj-gcc-debug $ ../gcc-3.4.6/configure --target=newARM --prefix=/usr/local/ tools --enable-languages=c --disable-shared --disable-thread --disable-nl s --with-headers=../newlib-1.13.0-spxk7/newlib/libc/include/ --with-newlib Here newARM is the new vendor target, the compiler is ported for new target. raja.saleru@raja ~/obj-gcc-debug $ make STAGE1_CFLAGS="-g3 -O0" all-stage1 make: *** No rule to make target `all-stage1'. Stop. raja.saleru@raja ~/k6mode/obj-gcc-debug $ make STAGE1_CFLAGS="-g3 -O0" The Makefile doesn't accept "all-stage1" how should we proceed ? If we omit the all-stage, it compiles, and then we did $ make install Now the folder /usr/local/tools contains the cross compiler "newARM-gcc". tried to debug the same $ ddd newARM-gcc The ddd does not contails all the source files of the compiler, but it has only few c and h files. Please help us how to proceed further to debug the gcc. Thanks Raja > raja.saleru@xxxxxxxxxxxxxx writes: > >> Can anybody explain about the unspec_volatile() rtl template usage, >> sample >> example and the purpose of it. > > unspec_volatile is documented in the gcc internals manual. There are > many examples of using it in the existing gcc backends. The purpose > is to permit describing instructions which can not be adequately > expressed in RTL, such as the x86 cld instruction. > > >> somebody can explain the procedure for gcc debugging ? > > http://gcc.gnu.org/wiki/DebuggingGCC > > > The mailing list gcc@xxxxxxxxxxx is intended for use by the gcc > developers. Please consider taking general questions to the mailing > list gcc-help@xxxxxxxxxxxx Thanks. > > Ian >
