From: Joel Brobecker <brobecker@adacore.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sourceware.org, David Ung <davidu@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Sign-extend pointers for n32
Date: Fri, 21 Dec 2007 04:36:00 -0000 [thread overview]
Message-ID: <20071221042337.GI6154@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0712201700380.16321@perivale.mips.com>
> > I think there's still a problem here, though it is somewhat endemic to
> > the argument passing routines:
> >
> > TYPE_CODE_ENUM, /* Enumeration type */
> > TYPE_CODE_REF, /* C++ Reference types */
> > TYPE_CODE_CHAR, /* *real* character type */
> > TYPE_CODE_BOOL,
> >
> > And possibly TYPE_CODE_MEMBERPTR too... that's a signed offset,
> > probably 32-bit in the n32 case. Getting this right is a real
> > pain.
>
> Hmm, these are obviously C-style types and I would expect other languages
> to have their own specific ones (Ada, anyone?).
Are you asking which TYPE_CODE enumerates are specific to Ada?
I don't think there are any. I had a quick look at the current list,
and nothing stood out.
--
Joel
next prev parent reply other threads:[~2007-12-21 4:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 14:43 Maciej W. Rozycki
2007-12-16 18:49 ` Daniel Jacobowitz
2007-12-19 15:27 ` Maciej W. Rozycki
2007-12-19 15:28 ` Daniel Jacobowitz
2007-12-19 16:16 ` Maciej W. Rozycki
2007-12-19 17:08 ` Daniel Jacobowitz
2007-12-20 16:41 ` Maciej W. Rozycki
2007-12-20 17:07 ` Daniel Jacobowitz
2007-12-20 17:18 ` Maciej W. Rozycki
2007-12-20 19:37 ` Daniel Jacobowitz
2007-12-21 4:36 ` Joel Brobecker [this message]
2007-12-21 11:34 ` Maciej W. Rozycki
2007-12-21 11:51 ` Joel Brobecker
2007-12-21 12:02 ` Maciej W. Rozycki
2007-12-22 5:30 ` Joel Brobecker
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=20071221042337.GI6154@adacore.com \
--to=brobecker@adacore.com \
--cc=davidu@mips.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.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