From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC 2nd] New file fpc-abi.c
Date: Wed, 19 Feb 2003 17:06:00 -0000 [thread overview]
Message-ID: <20030219170630.GB7961@nevyn.them.org> (raw)
In-Reply-To: <5.0.2.1.2.20030219165937.026bdc30@ics.u-strasbg.fr>
On Wed, Feb 19, 2003 at 05:38:49PM +0100, Pierre Muller wrote:
>
>
> This is a second version of fpc-abi.c patch.
> I tried to take into account all remarks I got.
>
> I checked all functions inside fpc-abi.c,
> modified most of them, removed part of the C++ specific code,
> but also left other parts,
> because FPC could support such things later or because
> C ++ classes might land there by error.
C++ classes should not land there by error. Please don't. If you want
to support debugging FPC code linked to C++ code, then eventually we
will need to support different ABIs per compilation unit. Until then,
the user is responsible for specifying the right one.
And it's just as likely it will be GCC v3 as v2, so leaving the v2 code
there is not useful.
> + This program is free software; you can redistribute it and/or
> + modify
> + it under the terms of the GNU General Public License as published
> + by
Your line wrapping is all messed up. Please run this through
gdb_indent.sh, and then eyeball it to make sure things look right.
> +/* #include <ctype.h> */
That should be removed.
> +/* 19-02-2003: Free Pascal only knows complete destructors. */
Please use ISO dates, since they're less ambiguous. That would be
2003-02-19.
> + /* We don't have an fcontext (e.g. the program was compiled with
> + g++ version 1). Try to get the vtbl from the TYPE_VPTR_BASETYPE.
> + This won't work right for multiple inheritance, but at least we
> + should do as well as GDB 3.x did. */
Comments to g++ version 1 and GDB 3.x shouldn't be in a new file for
Free Pascal support in GDB 5.4. If this code isn't appropriate for
Free Pascal it should be deleted or replaced with an error.
> +/* Return true if the INDEXth field of TYPE is a virtual baseclass
> + pointer which is for the base class whose type is BASECLASS.
> + 19-02-2003: Free Pascal does not support virtual base classes.
> + Leave that code active in case a C++ class lost its way here. */
Ditto.
> + /* Free Pascal does not support virtual base classes. */
> + /* First look for the virtual baseclass pointer
> + in the fields. */
Then the code shouldn't be here.
Would you mind fixing those and reposting it? Then I can look at the
actual code more closely. I'm still thinking about the issues involved
in using the "current C++ ABI" to handle "Free Pascal". I guess it'll
work...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-02-19 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:16 [RFC] " Pierre Muller
2003-02-17 17:31 ` Daniel Jacobowitz
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 [this message]
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=20030219170630.GB7961@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@cerbere.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