From: DJ Delorie <dj@redhat.com>
To: "Jayant R. Sonar" <Jayant.Sonar@kpitcummins.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Supporting multiple pointer sizes in GCC
Date: Fri, 25 Mar 2011 17:39:00 -0000 [thread overview]
Message-ID: <xnr59vrtii.fsf@greed.delorie.com> (raw)
In-Reply-To: <371569CBCFB2E745B891DBB88B2DFDDD1A229C5E3A@KCINPUNHJCMS01.kpit.com> (Jayant R. Sonar's message of "Fri, 25 Mar 2011 18:01:05 +0530")
"Jayant R. Sonar" <Jayant.Sonar@kpitcummins.com> writes:
> Is it possible to support multiple pointer sizes (e.g. 16bit, 32bit)
> which can co-exist in single compilation unit?
> Whether it is supported in GCC now?
> Is there any other architecture which has this feature already
> implemented?
Yes, there are three that I know of - mips64, s390 (tpf), and m32c.
Although, these days, you might be better served by looking into the
named-address-space stuff instead.
next prev parent reply other threads:[~2011-03-25 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 12:33 Jayant R. Sonar
2011-03-25 17:39 ` DJ Delorie [this message]
2011-03-25 17:53 ` Paul Koning
2011-03-25 18:51 ` DJ Delorie
2011-03-28 12:27 ` Jayant R. Sonar
2011-03-30 13:37 ` Claudiu Zissulescu
2011-03-31 13:45 ` Paulo J. Matos
2011-04-21 22:21 ` Michael Meissner
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=xnr59vrtii.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=Jayant.Sonar@kpitcummins.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).