From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joost van der Sluis <joost@cnoc.nl>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: Patch for pascal-dynamic arrays
Date: Mon, 05 Oct 2009 14:43:00 -0000 [thread overview]
Message-ID: <20091005144308.GA15831@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <1254737231.3257.20.camel@wsjoost.cnoc.lan>
On Mon, 05 Oct 2009 12:07:11 +0200, Joost van der Sluis wrote:
> On Sun, 2009-10-04 at 16:17 +0200, Jan Kratochvil wrote:
...
> > * Are the new Pascal testcase FAILures expected? If a more recent fpc is
> > required the testcase should XFAIL, not FAIL.
>
> Yes, they need a new fpc-version (2.3.1 or higher).
So the testcase should check the version (or if the seen behavior is clear it
is the old version) and setup_xfail appropriately.
> In principle, that information should be
> removed from 'struct main_type', since the lower_bound, upper_bound and
> length aren't defined for plain structures, without any address set.
This is again about the question whether dynamic types should be:
* fully dynamic, evaluating the bound value on each access by GDB code
(it was this way in the very first VLA patch version)
I was suggesting this solution in:
http://sourceware.org/ml/archer/2009-q2/msg00181.html
* static using check_typedef() as the current GDB codebase where a dynamic
type gets instantiated into its static type variant before it gets used
(this is the current VLA patch version)
One needs object_address for the instantiation but not later.
Your patch goes +/- the latter way by the instaniation (via field
`checked_dynamics') but still it would require to change all the functions
handling `struct type *' for possible arrays as even after the instantiation
`struct type *' is not enough there'.
Anyway if it gets regression-free I am fine with including it into
archer-jankratochvil-vla in its current form (after reviewing of the
regression-free form). But still for FSF GDB HEAD I would like to see
introducing something like `struct dynamic_type *' evaluated dynamically and
requiring object_address for it while being passed as normal `struct type *'
to the legacy parts of GDB. One should not be able to interchange
pre-check_typedef() and post-check_typedef() types in the code as they are two
different kinds. But that is not done now.
Thanks,
Jan
next prev parent reply other threads:[~2009-10-05 14:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 14:45 Joost van der Sluis
2009-09-16 15:45 ` Jan Kratochvil
2009-09-16 18:18 ` Joost van der Sluis
2009-09-16 18:41 ` Jan Kratochvil
2009-09-16 19:09 ` Joost van der Sluis
2009-09-30 16:00 ` Joost van der Sluis
2009-10-04 14:17 ` Jan Kratochvil
2009-10-05 10:08 ` Joost van der Sluis
[not found] ` <1254737231.3257.20.camel@wsjoost.cnoc.lan>
2009-10-05 14:43 ` Jan Kratochvil [this message]
2009-10-28 17:35 ` Joost van der Sluis
2009-10-30 9:47 ` Jan Kratochvil
2009-11-07 21:49 ` Joost van der Sluis
2010-04-12 11:25 ` Joost van der Sluis
2010-04-12 19:51 ` Jan Kratochvil
2010-04-14 10:35 ` Joost van der Sluis
2010-05-06 23:05 ` Jan Kratochvil
2010-05-14 21:58 ` Joost van der Sluis
2010-05-14 22:46 ` Jan Kratochvil
2010-05-15 20:24 ` Joost van der Sluis
2010-05-15 21:44 ` Jan Kratochvil
2010-05-16 12:04 ` Jonas Maebe
2010-05-16 17:06 ` Joost van der Sluis
2010-05-16 17:31 ` Jan Kratochvil
2010-05-16 21:49 ` Jonas Maebe
2010-05-16 21:55 ` Jonas Maebe
2010-05-16 18:31 ` Jan Kratochvil
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=20091005144308.GA15831@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@sourceware.org \
--cc=joost@cnoc.nl \
/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).