From: Johannes Stezenbach <js@convergence.de>
To: linux-mips@oss.sgi.com
Subject: Re: Mips16 toolchain?
Date: Tue, 26 Mar 2002 19:53:36 +0100 [thread overview]
Message-ID: <20020326185336.GA6017@convergence.de> (raw)
In-Reply-To: <20020325135834.GA1736@convergence.de>
First of all, many thanks for your help!
I wrote:
> $ mips-linux-gcc -mips16 -Wall -S t16.c
> t16.c: In function `main':
> t16.c:8: Internal compiler error:
Non-PIC mips16 compilation seems to work with gcc-2.95.4-debian:
$ mips-linux-gcc -fno-pic -mno-abicalls -mips16 -Wall -c t16.c
yields a t16.o, which looks good when disassembled with
mips-linux-objdump.
Now I need a non-PIC version of libgcc to link against,
since mips-linux-ld cannot link PIC with non-PIC code.
I had built a non-PIC libgcc for earlier dietlibc experiments,
but discarded it in favor of a less experimental development
environment...
I feel I have to learn more about the Linux kernel's role
when executing mips16 code (unaligned.c etc.), and experiment
more with my toolchain, until I know what I'm really doing ;-)
I will post here when I have any meaningful results.
Regards,
Johannes
next prev parent reply other threads:[~2002-03-26 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 13:58 Mips16 toolchain? Johannes Stezenbach
2002-03-25 14:59 ` Kevin D. Kissell
2002-03-25 14:59 ` Kevin D. Kissell
2002-03-26 8:10 ` Carsten Langgaard
2002-03-25 18:13 ` Dominic Sweetman
2002-03-26 18:53 ` Johannes Stezenbach [this message]
[not found] <no.id>
2002-03-25 20:37 ` Hartvig Ekner
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=20020326185336.GA6017@convergence.de \
--to=js@convergence.de \
--cc=linux-mips@oss.sgi.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