From: Ousama Rawas <orawas@gmail.com>
To: Arturas Moskvinas <arturas.moskvinas@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Compiling GCC 4.0.0 for mips r4000
Date: Sun, 31 Jul 2005 15:10:00 -0000 [thread overview]
Message-ID: <cc28937c0507310809104b7e13@mail.gmail.com> (raw)
In-Reply-To: <4a618d080507310600305aabd1@mail.gmail.com>
On 7/31/05, Arturas Moskvinas <arturas.moskvinas@gmail.com> wrote:
> > Acctually, I think I'll try --target=mips64-linux (I'm not sure what
> > specific operating system I'll be using at this point). What should I
> > do though if I want to compile stuff for the mips r4000 specifically,
> > irrespective of the OS to be used?
>
> You want to write your own OS, or BIOS? Because different OS'es have
> different calling conventions and so on, it is impossible to have a
> one compiler for every OS for that architecture... Of course you can
> compile all possible compiler for that architecture...
>
> Arturas M.
>
Hey...
Thanks for the reply. What I need is to assume any OS at this point,
and to compile for the mips r4000. At a layer stage, I might
write/customize an OS. Now I just need to compile GCC to generate
assembly code for the mips r4000, assuming that I have this or that OS
(specifying an OS at this point isn't really essential for me).
Thanks for the help.
Ousama Rawas
next prev parent reply other threads:[~2005-07-31 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 21:31 Meissner, Michael
2005-07-31 9:36 ` Ousama Rawas
[not found] ` <4a618d080507310600305aabd1@mail.gmail.com>
2005-07-31 15:10 ` Ousama Rawas [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-01 17:06 Meissner, Michael
2005-07-27 10:37 Recompiling GCC just won't work Ousama Rawas
2005-07-29 18:45 ` Compiling GCC 4.0.0 for mips r4000 Ousama Rawas
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=cc28937c0507310809104b7e13@mail.gmail.com \
--to=orawas@gmail.com \
--cc=arturas.moskvinas@gmail.com \
--cc=gcc-help@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).