Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Simulator dv-sockser.o patch testing
Date: Mon, 25 Mar 2013 07:40:00 -0000	[thread overview]
Message-ID: <514FB8F2.9060702@oarcorp.com> (raw)

`Hi

I tested three configurations:

+ gdb 7.5.91 as baseline
+ gdb head with my last acinclude.m4 patch
+ gdb head with Mike's acinclude.m4 patch

I tested these 10 targets [1]:

bfin-elf cris-elf frv-elf iq2000-elf lm32-elf m32r-elf
m68hc11-elf mips-elf mn10300-elf sh64-elf

with: (1) no simulator option, (2) --disable-sim-hardware
and (3) --enable-sim-hardware

This is a total of 30 builds.

gdb 7.5.91 and my patch built 27 of the 30 and failed to
bfin-elf, m68hc11-elf, and mn10300-elf with --disable-sim-hardware.
Mike's patch let them all build.

The only discrepancy in the make check summary was that
WITH Mike's patch cris-elf with --enable-sim-hardware has this:

=== sim Summary ===
# of expected passes 304
# of untested testcases 136

In the 7.5.91 log, the 136 was 170.

I know absolutely nothing about cris and only ran this because
the configure file changed after running autoconf. Nothing specific
to the cris was changed. This could be something else going on.

As far as I can tell, Mike's patch is an improvement over mine
and what was in 7.5.91. If he regenerates the configure scripts
that need it, I would be perfectly happy with his patch being
applied.

This is the set of files which were touched by his patch or
regenerated in my tree:

#    modified:   sim/bfin/configure
#    modified:   sim/common/acinclude.m4
#    modified:   sim/cris/configure
#    modified:   sim/frv/configure
#    modified:   sim/iq2000/configure
#    modified:   sim/lm32/configure
#    modified:   sim/m32r/configure
#    modified:   sim/m68hc11/configure
#    modified:   sim/mips/configure
#    modified:   sim/mn10300/configure
#    modified:   sim/sh64/configure

Mike, can you commit yours? Please. :)

[1] I forgot to include mipstx39-elf in the targets built against
all three versions. I did run it against Mike's by hand and it is OK.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985


             reply	other threads:[~2013-03-25  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  7:40 Joel Sherrill [this message]
2013-03-26 11:50 ` Hans-Peter Nilsson
2013-03-26 13:55   ` Hans-Peter Nilsson
2013-03-26 17:12     ` Joel Sherrill
2013-03-26 19:16       ` Hans-Peter Nilsson

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=514FB8F2.9060702@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gdb-patches@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