From: Kai Ruottu <karuottu@mbnet.fi>
To: gcc-help@gcc.gnu.org
Cc: sameer0201@gmail.com
Subject: Re: it'urgent please help me!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Date: Tue, 20 Feb 2007 11:01:00 -0000 [thread overview]
Message-ID: <45DABC1E.8090701@mbnet.fi> (raw)
In-Reply-To: <45DAA0E2.8010904@codesourcery.com>
sameer sinha wrote:
>> Please can any one tell me how to bulid gcc newer version for
>> generating code for i960MC processor.
Newer than which GCC version?
>>
>> is there any switch to generate coed for i960MC or i will have to
>> build it first
>> for target i960.
The switch seems to be '-mmc' for i960MC code generation.... As
default for instance
a gcc-3.2.3 for 'i960-coff' produces code for something 'generic' but
multilibs for
'soft-float' and 'ld64' (whatever this then means) will be produced but
no 'i960MC'
optimized libraries without first patching the GCC sources to do this...
>>
>> Right now i am using Linux i686.
Building cross GCCs on Linux i686 should be a piece of cake...
>>
>> And also tell me whether it's possible to generate i960Mc code
>> for language Ada95 or it is only possible for language "C" ???????
I'm not a specialist in Ada but I would expect this language requiring
the target to be a
"system" like "Linux", "VxWorks", "RTEMS" etc. with a "file system" in
it, so that things
like 'dirent.h' would exist among its target headers. An embedded
target like 'i960-coff'
isn't this kind of "system target" !
So before you will tell your target type, not only the CPU type, it is
totally vain to discuss
about any "how to build a cross GCC for the i960-system-x" issues. What
I told being a
"piece of cake", was producing a cross GCC for 'i960-coff' with the
gcc-3.2.3 sources. But
the 'i960-wrs-vxworks' target can be totally another thing :-(
prev parent reply other threads:[~2007-02-20 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1c1f08070702192245n303b4bc2j312ce5547b3ff5ff@mail.gmail.com>
2007-02-20 8:52 ` Brooks Moses
2007-02-20 11:01 ` Kai Ruottu [this message]
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=45DABC1E.8090701@mbnet.fi \
--to=karuottu@mbnet.fi \
--cc=gcc-help@gcc.gnu.org \
--cc=sameer0201@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).