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>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: Patch for pascal-dynamic arrays
Date: Wed, 16 Sep 2009 18:18:00 -0000	[thread overview]
Message-ID: <1253125058.1180.17.camel@wsjoost.cnoc.lan> (raw)
In-Reply-To: <20090916154453.GA23913@host0.dyn.jankratochvil.net>

On Wed, 2009-09-16 at 17:44 +0200, Jan Kratochvil wrote:
> On Mon, 14 Sep 2009 16:45:29 +0200, Joost van der Sluis wrote:
> > Attached is the patch I have so far, including some tests.
> 
> Please fix it so that it builds with -O2 -Wall -Werror, it also does not
> follow the GNU coding style (such as space after a function name).

Thanks for your comments and your patch. I had tested everything without
optimisation (for debugging) and -Werror because that doesn't compile on
windows.

> Then also please check regressions of the testsuite - `make -C gdb check' and
> comparing gdb.sum before/after the patch.

About the testsuite... it takes ages to complete. Is there some way to
run just one test (or just one .exp test-file?)

> I had to do some of these fixes but it has too many regressions.

I don't know anything about the GNU coding style, in fact, I know
nothing about c. This is the first c code I wrote in my whole live. That
makes fixing the regressions on c-code hard. But I think that there are
only a few issues which will fix a lot of regressions. I'll have a look
at them.

Just a remark: some of your changes in the coding-style are corrections
for portions of the code that I copy-pasted from other parts. I use the
gdb-code as 'example-code' for the coding style. Is this generally a
save assumption, or are there a lot of issues regarding the coding-style
in the gdb-code?

Joost

  reply	other threads:[~2009-09-16 18:18 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 [this message]
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
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=1253125058.1180.17.camel@wsjoost.cnoc.lan \
    --to=joost@cnoc.nl \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).