From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: joel.sherrill@oarcorp.com
Cc: gdb-patches@sourceware.org
Subject: Re: Recent simulator patches broke many sims
Date: Sun, 24 Mar 2013 02:53:00 -0000 [thread overview]
Message-ID: <201303240000.r2O00xZQ007925@ignucius.se.axis.com> (raw)
In-Reply-To: <514E3CFA.4080406@oarcorp.com> (message from Joel Sherrill on Sun, 24 Mar 2013 00:38:34 +0100)
Host is some Debian; x86_64-linux.
> From: Joel Sherrill <joel.sherrill@oarcorp.com>
> Date: Sun, 24 Mar 2013 00:38:34 +0100
> I have a fix.
Great. Thanks for attending to this so quickly.
But the patch seems mingw-specific and a host with x64_64-linux
probably still fails. Or is "host" actually the target here?
> I suspect I need to do the right thing and commit a bunch.
Just please test-build and *really* preferably regression-test
each affected simulator. (Build and install binutils for it.)
When they're broken I guess expediting a fix might require
less...
> Hans.. I still think your auto-tester must not include sh64-elf or it
> hadn't gotten to it yet.
That's right, I'm not testing all simulators, that's why I wrote
*some* simulators and *including*. The set of simulators was
what built and was error free some-long-time-ago.
> And it may need to test with the 3 configure
> options I listed earlier for completeness.
No, I'm not aiming for completeness, the autotester is there
only to check that people do the bare essentials as to test
before checking in. 1/2 ;)
brgds, H-P
next prev parent reply other threads:[~2013-03-24 0:01 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 [this message]
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
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=201303240000.r2O00xZQ007925@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=gdb-patches@sourceware.org \
--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