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

[-- Attachment #1: Type: Text/Plain, Size: 1429 bytes --]

On Sunday 24 March 2013 19:23:28 Hans-Peter Nilsson wrote:
> > From: Joel Sherrill <joel.sherrill@oarcorp.com>
> > Date: Sun, 24 Mar 2013 15:45:27 +0100
> > 
> > This came in after I was done email last night. My test
> > run finished overnight with no horribly bad issues. I have no idea
> > what the make check results should be though and they could be
> > because I simply ran "make check" with no board specified and
> > no gcc for the target installed.
> 
> This would be no news to *you*, but for the record:
> 
> You need a board (make check RUNTESTFLAGS=--target_board=$board
> with e.g. board=cris-sim).  All boards are in "recent"
> dejagnu-1.5 IIRC and most in ancient dejagnu-1.4.4.  You need
> installed binutils (e.g. in some temp location added to PATH for
> the duration of the test-run) for each sim configuration as
> mentioned.  I don't run with target gcc; not needed for the
> level of smoke test I'm after and I guess not for this change
> either.

that's not entirely true.  many (all but cris?) sims run & pass just fine 
without needing to explicitly pass magic flags.  i know the Blackfin and frv 
sims can build & run pretty much all their tests w/out requiring board flags.

imo, requiring manual board selection like this is archaic for no good reason.  
i never test sims with specific flags, nor do i plan on starting.  `make check-
sim` is my limit of testing.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-03-26 16:21 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 [this message]
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
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=201303261225.40691.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hans-peter.nilsson@axis.com \
    --cc=joel.sherrill@oarcorp.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