From: "Paulo J. Matos" <pocmatos@gmail.com>
To: gcc@gcc.gnu.org
Subject: Re: Supporting multiple pointer sizes in GCC
Date: Thu, 31 Mar 2011 13:45:00 -0000 [thread overview]
Message-ID: <in1s8p$hhm$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTi=Z5MAUAwUCZM3L5GXwBsjNs7y3sxSZHOfzoAUU@mail.gmail.com>
On 30/03/11 08:57, Claudiu Zissulescu wrote:
> Hi,
>
> I would try using the named address space for your issue (see
> TARGET_ADDR_SPACE_POINTER_MODE). Please check the SPU target for an
> implementation example.
>
Hummm, I haven't noticed this hook before. Could this be used to
implement cases where function pointers have a different size than data
pointers (as in harvard archs). It looks like it but can someone confirm?
Cheers,
--
PMatos
next prev parent reply other threads:[~2011-03-31 12:32 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
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 [this message]
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='in1s8p$hhm$1@dough.gmane.org' \
--to=pocmatos@gmail.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).