Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: vapier@gentoo.org
Cc: joel.sherrill@oarcorp.com, gdb-patches@sourceware.org
Subject: Re: Recent simulator patches broke many sims
Date: Tue, 26 Mar 2013 20:50:00 -0000	[thread overview]
Message-ID: <201303261935.r2QJZOXc017297@ignucius.se.axis.com> (raw)
In-Reply-To: <201303261415.19076.vapier@gentoo.org> (message from Mike	Frysinger on Tue, 26 Mar 2013 19:15:17 +0100)

> From: Mike Frysinger <vapier@gentoo.org>
> Date: Tue, 26 Mar 2013 19:15:17 +0100

> On Tuesday 26 March 2013 13:12:38 Hans-Peter Nilsson wrote:
> i see it the other way.  doing `make check` for all these
> packages work w/out the user having to dig into esoteric tools
> (that often times lack documentation, or any real semblance of
> an entry point).
> 
> for binutils/gcc/etc..., there are plenty of
> compile/link/etc... tests that can be done without needing to
> know about a board.  the sim is special in that testing it
> requires running code,

Thinking you're good without running any runnnable tests?
I guess we have to agree to disagree here.

> so it's entirely reasonable for the
> default `make check` to setup a state where the tests actually
> work.

You know, if someone went to do the work to provide a default
(overridable) target-board for all cross *-elf et al targets at
the toplevel, I wouldn't mind.

I'll just add that you're wrong if you think gcc testing without
*running* the runnable tests is to be taken seriously (with very
few exceptions).  I haven't ran gdb tests recently enough to
remember it, but...

brgds, H-P


  reply	other threads:[~2013-03-26 19:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24  0:22 Hans-Peter Nilsson
2013-03-24  0:38 ` Joel Sherrill
2013-03-24  5:39   ` Hans-Peter Nilsson
2013-03-24  5:39     ` Joel Sherrill
2013-03-24 11:04       ` Hans-Peter Nilsson
2013-03-24  2:12 ` Joel Sherrill
2013-03-24  2:35 ` Joel Sherrill
2013-03-24  2:53   ` Hans-Peter Nilsson
2013-03-24  5:22     ` Hans-Peter Nilsson
2013-03-24  5:36     ` Hans-Peter Nilsson
2013-03-24  4:51   ` Hans-Peter Nilsson
2013-03-24 11:33   ` Mike Frysinger
2013-03-25  3:30     ` Joel Sherrill
2013-03-25  3:50       ` Hans-Peter Nilsson
2013-03-25  7:39         ` Joel Sherrill
2013-03-26 17:49         ` Mike Frysinger
2013-03-26 18:41           ` Hans-Peter Nilsson
2013-03-26 18:43             ` Joel Sherrill
2013-03-26 19:49             ` Mike Frysinger
2013-03-26 20:50               ` Hans-Peter Nilsson [this message]
2013-03-26 21:24                 ` Mike Frysinger
2013-03-27  1:39                   ` Hans-Peter Nilsson
2013-03-27  9:13                     ` Mike Frysinger
2013-03-26 18:56     ` Mike Frysinger
2013-03-27  8:47       ` Joel Brobecker
2013-03-27  8:50         ` Hans-Peter Nilsson
2013-03-27 18:38           ` Joel Sherrill
2013-03-27 19:01             ` Joel Brobecker
2013-03-27 19:43             ` Joel Brobecker

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=201303261935.r2QJZOXc017297@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joel.sherrill@oarcorp.com \
    --cc=vapier@gentoo.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