From: Kenneth Porter <shiva@well.com>
To: help-gcc@gnu.org
Subject: Re: GCC for SHARC port to PC (numerical C)
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <38754F47.BDF3113D@well.com> (raw)
Message-ID: <20000401000000.GTeApNFVCugkxvbo1wPRU66gsHBmi5EtV29Cknrz96s@z> (raw)
In-Reply-To: <852but$f42$1@newnews.mikom.csir.co.za>
mj wrote:
>
> Hi
> The gcc port by ADI for the sharc includes numerical extensions to the C
> language (vector, complex arithmetic). I am interested in developing code
> on a PC and port it to the SHARC at a later stage. I would like to compile
> numerical C codes with gcc on a PC without a SHARC. Does anybody have
> experience with this? Must I recompile the compiler for the PC?
> TYIA
> Marthinus
I think Gnu adopted the numeric extensions at one point, but I don't
know if they're in the current generation of the compiler. There *is* a
PC port of gcc. Check out Cygwin ( http://sourceware.cygnus.com/cygwin/ )
for example.
next parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <852but$f42$1@newnews.mikom.csir.co.za>
2000-01-06 18:33 ` Kenneth Porter [this message]
2000-01-07 10:41 ` Alan Lehotsky
2000-04-01 0:00 ` Alan Lehotsky
2000-04-01 0:00 ` Kenneth Porter
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=38754F47.BDF3113D@well.com \
--to=shiva@well.com \
--cc=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).