From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New file fpc-abi.c
Date: Mon, 17 Feb 2003 17:31:00 -0000 [thread overview]
Message-ID: <20030217173108.GA19560@nevyn.them.org> (raw)
In-Reply-To: <5.0.2.1.2.20030217180426.02227540@ics.u-strasbg.fr>
On Mon, Feb 17, 2003 at 06:12:17PM +0100, Pierre Muller wrote:
> This patch adds a new file fpc-abi.c
> to the gdb directory.
>
> The purpose of this file is rather clear:
> it allows to recognize Free Pascal compiled
> objects and to handle ABI stuff in a more
> adequate way.
>
> Should I submit this in several RFA?
>
>
> ChangeLog entry:
>
> 2003-02-17 Pierre Muller <muller@ics.u-strasbg.fr>
>
> * fpc-abi.c: New file.
> Implements Free Pascal specific ABI.
> * minsyms.c (install_minimal_symbols): Recognize
> Free Pascal compiled objects by the presence of
> 'fpc_compiled' minimal symbol.
> * Makefile.in: Add fpc-abi.c compilation rules.
A lot of this file looks like it was just copied from one of the GNU
C++ ABI files. Certainly the comments are now wrong. Is a lot of the
code really appropriate? i.e. does Free Pascal have the concept of an
RTTI type, or virtual functions, or operator names?
These are listed as C++ ABIs. Adding one for Pascal feels dodgy.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-17 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:16 Pierre Muller
2003-02-17 17:31 ` Daniel Jacobowitz [this message]
2003-02-18 8:17 ` Pierre Muller
2003-02-18 14:45 ` Daniel Jacobowitz
2003-02-18 21:20 ` Andrew Cagney
2003-02-19 16:42 ` [RFC 2nd] " Pierre Muller
2003-02-19 17:06 ` Daniel Jacobowitz
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=20030217173108.GA19560@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@ics.u-strasbg.fr \
/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