public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Joost van der Sluis <joost@cnoc.nl>
To: Project Archer <archer@sourceware.org>
Subject: Re: Patch for pascal-dynamic arrays
Date: Mon, 05 Oct 2009 10:08:00 -0000	[thread overview]
Message-ID: <1254737294.3257.21.camel@wsjoost.cnoc.lan> (raw)
In-Reply-To: <20091004141705.GA18527@host0.dyn.jankratochvil.net>

On Sun, 2009-10-04 at 16:17 +0200, Jan Kratochvil wrote:
> On Wed, 30 Sep 2009 17:59:34 +0200, Joost van der Sluis wrote:
> > Attached it the new patch.
> 
> Please write GNU style ChangeLog entry for it.  I am sorry I did not write the
> entries myself in the log (as a partial excuse it was not reviewed by anyone
> that time).
> 
> 
> > I tested it and I have no regressions anymore.
> 
> Getting a lot of regressions included below.

I had no Fortran installed.

> * Some fortran failures only happen with `ulimit -v 500000'.
> * 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).

> > @@ -197,6 +198,13 @@ struct value
> >    /* If value is a variable, is it initialized or not.  */
> >    int initialized;
> >  
> > +  CORE_ADDR data_address;
> > +
> > +  char calc_length;
> > +  long length;
> > +  char checked_dynamics;
> > +  long lower_bound;
> > +  long upper_bound;
> 
> 
> Still I do not like duplicating the information already present in `struct
> main_type'.  I find right you have changed passing some `struct type *' to
> `struct value *' instead but that new `struct value' just could use
> copy_type_recursive on that linked `struct type'.

I didn't thought about that. 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. But
that would be far to intrusive. But I wanted to do it as 'clean' as
possible, that's why the duplication.

I'll look if I can fix it without the duplication as you suggested.

Thanks for looking at it,

Joost 

  reply	other threads:[~2009-10-05 10:08 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 [this message]
     [not found]       ` <1254737231.3257.20.camel@wsjoost.cnoc.lan>
2009-10-05 14:43         ` Jan Kratochvil
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=1254737294.3257.21.camel@wsjoost.cnoc.lan \
    --to=joost@cnoc.nl \
    --cc=archer@sourceware.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).