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: gdb-patches@sourceware.org
Subject: Re: [RFC 0/4] Fix recent sim/*/config.in fallout: frv, m32r, sh64, iq2000
Date: Tue, 24 Mar 2015 04:18:00 -0000	[thread overview]
Message-ID: <20150324041856.GC10761@vapier> (raw)
In-Reply-To: <201408230313.s7N3DFps018785@ignucius.se.axis.com>

[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]

On 23 Aug 2014 05:13, Hans-Peter Nilsson wrote:
> From: Hans-Peter Nilsson <hp@axis.com>
> > Recently, a change requiring -ldl due to bfd plugin default changing
> > from off to on, spread throughout the generated configury files, for
> > simulators as well as gdb.  In that process, sim/*/config.in for the
> > sims below was regenerated for the first time since 2012.  This had
> > build-breaking fallouts for some simulator showing bloopers in changes
> > from around 2013-03-23, attempts enabling sim-hardware and
> > dv-sockser.o.  Here's my take on fixing that: let's return to the
> > state before those attempts.  This is a request-for-comments, I'll
> > commit this in a few days unless someone has a better idea, one that
> > lets these simulators build *without* --{enable,disable} options and
> > where committing this would still not be an incremental improvement.
> 
> Now committed.  I'll stop here, noting that possible further cleanups
> would be to fix the buggy SIM_AC_OPTION_HARDWARE and decouple the
> prerequisites for dv-sockser.o from the act of actually enabling it
> (e.g. the now combined effect of HAVE_DV_SOCKSER).  Please also, if
> you consider "re-enabling" simulated hardware for these sims, first
> investigate whether all the wires and plumbing is in place for it to
> actually make a difference in function for the particular sim.  Also,
> test-cases for the enabled simulated hardware would be helpful, even a
> simple "hello, world" to a simulated serial port.

i've finished landing a series of changes into master that can be summarized:
 - clean up dv-sockser code to centralize its enabled/disabled logic
 - let the common code handle building of dv-sockser all the time (sans mingw)
 - fix bugs around SIM_AC_OPTION_HARDWARE default enable
 - delete the broken uart code from frv devices

that leads me back to this patch series.  there's no longer a need to disable
hw in these sims by default, so i've somewhat reverted these changes by setting 
the default to "yes" for them.

testcases would certainly be nice, but i have no idea how to write ones for 
these ports.  i'll be pestering people in the future when they make updates to 
specific arches, and i'll be rejecting new sims that lack any tests.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-24  4:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  4:28 Hans-Peter Nilsson
2014-08-23  3:13 ` Hans-Peter Nilsson
2015-03-24  4:18   ` Mike Frysinger [this message]
2015-03-24  5:55     ` Hans-Peter Nilsson
2015-03-24  4:19   ` [PATCH] sim: Revert "Fix frv/iq2000/m32r/sh64 sim, default hardware to off." Mike Frysinger

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=20150324041856.GC10761@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hans-peter.nilsson@axis.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