From: Thomas Schuetzkowski <Thomas.Schuetzkowski@web.de>
To: Alexandre Oliva <aoliva@cygnus.com>
Cc: gcc@gcc.gnu.org
Subject: Re: 8051, libgcc2.a, Internal compiler error in `instantiate_virtual_regs_1'
Date: Mon, 20 Mar 2000 12:25:00 -0000 [thread overview]
Message-ID: <38D68900.90DB528A@web.de> (raw)
In-Reply-To: <orn1ntmnbm.fsf@garnize.lsd.ic.unicamp.br>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Alexandre Oliva wrote:
>
> On Mar 20, 2000, Thomas Schuetzkowski <Thomas.Schuetzkowski@web.de> wrote:
>
> > Do I have to provide the header files (stdlib.h, unistd.h, ...)?
>
> Yep. newlib (at sourceware.cygnus.com) may supply the headers you
> need.
>
> > I only want the compiler to create assembler code for the 8051. Do I
> > need a libgcc2?
>
> Dunno, it depends on the target.
>
> > I also don´t have a archiver.
>
> Try GNU binutils
>
> > test1.i:5: Internal compiler error in `instantiate_virtual_regs_1', at function.c:4027
>
> Is this GCC off CVS or some stable release?
>
> --
> Alexandre Oliva Enjoy Guaraná, see http://www.ic.unicamp.br/~oliva/
> Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
> Free Software Developer and Evangelist CS PhD student at IC-Unicamp
> oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
I use gcc 2.95.2 with my own machine descrition. This is the first time
I´ve tied to
compile gcc for this new target.
When I use the header files from my host machine (i586-gnu-linux) and
copy them to
/usr/local/8051 the compilation of libgcc2 crashes also with
Internal compiler error in `instantiate_virtual_regs_1'
Thanks
Thomas
--
\|/ ______ \|/
"@'/ ,. \'@"
/__| \__/ |__\
\__U_/
next prev parent reply other threads:[~2000-03-20 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-20 11:38 Thomas Schuetzkowski
2000-03-20 11:52 ` Alexandre Oliva
2000-03-20 12:25 ` Thomas Schuetzkowski [this message]
2000-03-20 12:53 ` Alexandre Oliva
2000-03-20 14:48 ` Martin v. Loewis
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=38D68900.90DB528A@web.de \
--to=thomas.schuetzkowski@web.de \
--cc=aoliva@cygnus.com \
--cc=gcc@gcc.gnu.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).