This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [newb] GCC machine description help, modifying existing md
- From: Ian Lance Taylor <iant at google dot com>
- To: dhua026 dhua026 <dhua026 at aucklanduni dot ac dot nz>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 12 Mar 2009 18:28:42 -0700
- Subject: Re: [newb] GCC machine description help, modifying existing md
- References: <322416170903121652g31bd789eg66aba919479ca692@mail.gmail.com>
dhua026 dhua026 <dhua026@aucklanduni.ac.nz> writes:
> but most importantly, it used the "callz" instruction:
> /tmp/ccshjbUO.s: Assembler messages:
> /tmp/ccshjbUO.s:41: Error: no such instruction: `callz __fixunssfdi@PLT'
> /tmp/ccshjbUO.s:53: Error: no such instruction: `callz __fixunssfdi@PLT'
> make[1]: *** [_fixsfdi.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
>
> then it finally fails.
>
> Did I misunderstand what GCC stage 1 is and what I am trying to do is
> simply not feasible?
> What should I do to test out simple .md modifications?
Part of stage 1 involves building the runtime support library. This is
needed in order to build stage 2, since the stage 2 compiler will need
to be linked with some runtime support library. The failure above
occurred while building the runtime support library.
To build only the stage 1 compiler proper, and not the stage 1 runtime
library, use "make all-stage1-gcc".
Ian