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: Wed, 16 Sep 2009 18:41:00 -0000 [thread overview]
Message-ID: <20090916184106.GA2442@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <1253125058.1180.17.camel@wsjoost.cnoc.lan>
On Wed, 16 Sep 2009 20:17:38 +0200, Joost van der Sluis wrote:
> I had tested everything without optimisation (for debugging) and -Werror
> because that doesn't compile on windows.
Could you please run it also on GNU/Linux as some final test? If you do not
have one available there are various test boxes available at sourceforge.net
and similar sites or contact me offlist. Testsuite on GNU/Linux should IMO
catch most of the possible regressions.
> > 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.
One `make check' should take at most about 20 minutes in worst cases, some
5 minutes should be more normal. Sure it is being run just as a final test.
Many FAIL results are normal, just regressions are worth a check.
> Is there some way to run just one test (or just one .exp test-file?)
I use
cd gdb/testsuite
make site.exp # needed just once
runtest runtest gdb.base/start.exp
but probably more correct is to just run:
cd gdb/testsuite
make check RUNTESTFLAGS="gdb.base/start.exp"
> I don't know anything about the GNU coding style,
No problem just please try to follow the spacing/indentation of the code
around despite it looks unusual.
http://www.gnu.org/prep/standards/standards.html#Formatting
> But I think that there are only a few issues which will fix a lot of
> regressions. I'll have a look at them.
Yes, I agree, it may be even a single problem.
> 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.
:-) Some existing GDB code may not follow it but I do not know much of such
places offhand.
(The GNU coding style really was not a primary concern of my mail, feel free
to keep the code parts which you are not sure about the formatting intact.)
Thanks,
Jan
next prev parent reply other threads:[~2009-09-16 18:41 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 [this message]
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=20090916184106.GA2442@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).