This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: xgcc: Internal error: Killed (program cc1)


Most probably some other maillist could be better for this, like the
'gcc*@gnu.org' (or something) for GCC-developers, but before asking
this elsewhere, some elaborations/primary things should be done:

"Õŵ¤" <e_zhangdan@sina.com> wrote:

>     I'm working on proting GCC to a new processor.
>     I modify the mmix.h, mmix.md, mmix.c files.

 Telling what are the base sources, 'gcc-3.2.1', 'gcc-3.3'-snapshots,
some CVS-sources or what is more than essential... A GCC-porter is
expected to work with the up-to-date sources though, but some frozen
release sources like the current gcc-3.2.1 ones could be more
confortable for a newbie in porting...

> But when I emit the command:
>   make all
> then it tells me error messages:
> /home/zd/build-vp6/gcc/xgcc -B/home/zd/build-vp6/gcc/
> -B/home/zd/vp6/vp6/bin/ -B/home/zd/vp6/vp6/lib/
> -isystem /home/zd/vp6/vp6/include -S tmp-dum.c
> xgcc: Internal error: Killed (program cc1)

 Funny, anyone trying to port GCC for a new CPU is expected to have
the "Using and Porting the GNU Compiler Collection (GCC)", or the new
splitted manuals coming with gcc-3.x.  Ie. building the manual(s)
first using 'pdftex', 'tex'+'dvips' or something and then producing
500+ pages on a laser printer, is quite recommended -- if one doesn't
like those 'electronic manuals'. Using 'pdftex' produces a nice PDF-
doc with bookmarks and hyperlinks and Acroread handles it nicely. But
many still prefer nice text on paper...

 The Chapter/Section: "2.7 Options for Debugging Your Program or GCC"
for debugging GCC should be what you need to consult. The GCC-options
like:

----------------------------- clip ----------------------------------
-Q		Makes the compiler print out each function name as it is
		compiled, and print some statistics about each pass when it
		finishes.

-dletters
		Says to make debugging dumps during compilation at times
		specified by letters. This is used for debugging the compiler.
		The file names for most of the dumps are made by appending a
		word to the source file name (e.g. `foo.c.rtl' or `foo.c.jump').
		Here are the possible letters for use in letters, and their
		meanings:
----------------------------- clip ----------------------------------

are available...

 So, before disturbing the GCC-developers, you should do some
homework first, build the GCC-manual and try those debugging
options it documents...

 The 'gcc/doc' in the 'gcc-3.x' sources has those '.texi' sources
for the GCC-manuals but maybe there are prebuilt manuals available
on the net. The problem is that nobody puts them there if nobody
has any problems in producing them, as seems to be the case... No
demand, no supply...  I may be totally wrong, but some things hint
that not so many have the GCC-manual available but they are too
proud to tell about any problems...

Cheers, Kai


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]