From: "Ghanta, Bose" <bose.ghanta@stratus.com>
To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Cc: "Ghanta, Bose" <bose.ghanta@stratus.com>
Subject: Big-endian Gcc on Intel IA32
Date: Mon, 17 Dec 2001 12:00:00 -0000 [thread overview]
Message-ID: <95AE3CDB3543D511883A0020485B38B9028982D6@exna3.stratus.com> (raw)
Dar Gcc members,
Today we use GCC on PA-RISC a big-endian compiler. We like it a lot. We
would continue to use it in the current and future products at our company
(Stratus computer inc.).
We are now thinking of a platform migration to Intel IA32 platform. As you
all know Intel IA32 is a little endian processor family and GCC and all
other products run in little endian format on IA32. I need to address an
interoperability issue for our customers and big-endian GCC will solve some
part of this problem.
My question to you all is: Is there a big-endian GCC available on IA32?
If available, who is the source of
contact and what is the effort involved here?
Our current product is:
GCC is a native (big endian) compiler hosted and targeted to a
proprietary OS(VOS) on
a commodity (PA-RISC) processor. ELF is the object files.
Proprietary OS (VOS) and
follows mostly standard ABI.
Our future plan is:
Create GCC as a native (big endian) compiler hosted and targeted to
a proprietary OS (VOS) on
a commodity (IA-32) processor. ELF is the object files.
Proprietary OS (VOS) and follows mostly
standard ABI.
I would appreciate any help from you here.
My phone number is: (978) 461 7617
email is: Bose_Ghanta@stratus.com
Thank you,
Bose
next reply other threads:[~2001-12-17 19:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 12:00 Ghanta, Bose [this message]
2001-12-17 12:08 dewar
2001-12-17 13:10 ` Linus Torvalds
2001-12-17 14:00 ` Alan Lehotsky
2001-12-17 13:14 dewar
2001-12-17 13:42 ` guerby
2001-12-17 13:43 ` Linus Torvalds
2001-12-17 14:22 ` guerby
2001-12-17 14:52 ` Linus Torvalds
2001-12-17 15:01 ` Richard Henderson
2001-12-17 15:12 ` Linus Torvalds
2001-12-17 15:54 ` Richard Henderson
2001-12-17 17:43 ` Linus Torvalds
2001-12-17 18:12 ` Richard Henderson
2001-12-18 11:55 ` Jason Riedy
2001-12-17 16:43 ` Ross Smith
2001-12-18 1:28 ` Florian Weimer
2001-12-17 18:39 dewar
2001-12-17 18:59 ` Per Bothner
2001-12-18 3:49 dewar
2001-12-23 6:59 ` Florian Weimer
2001-12-18 11:41 Morten Welinder
2001-12-18 11:42 ` Phil Edwards
2001-12-18 14:48 ` Linus Torvalds
2001-12-19 11:47 Bernard Dautrevaux
2001-12-19 13:09 ` Linus Torvalds
2001-12-20 5:36 Etienne Lorrain
2001-12-23 7:06 dewar
2001-12-23 7:08 ` Florian Weimer
2001-12-23 7:26 dewar
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=95AE3CDB3543D511883A0020485B38B9028982D6@exna3.stratus.com \
--to=bose.ghanta@stratus.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).