Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: profile: implement --profile-file backend
Date: Thu, 22 Apr 2010 01:49:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1004212143050.79451@dair.pair.com> (raw)
In-Reply-To: <201004212039.35705.vapier@gentoo.org>

On Wed, 21 Apr 2010, Mike Frysinger wrote:
> sorry, i noticed i need these two fixes for some ports.  the ones i was build
> testing worked, but i wrote a small helper script to build all of them and
> noticed the problem.  wish sim had a --enable-targets=all option like gdb, but
> in the mean time, i'll stick with this script for future patches.
> -mike
>
> sim/frv/:
> 2010-04-21  Mike Frysinger  <vapier@gentoo.org>
>
> 	* profile.c (sim_profile_print_bar): Add cpu argument.

Please be much more careful when you test your patches.
(I think you forgot to run your script. ;)

Building all simulators seems reasonable to me, even so to test
those with test-suites (though it requires building binutils,
which thankfully can be checked out in the same source-tree).

Your change broke at least cris-elf, iq2000-elf and m32r-elf,
as you didn't adjust calls in sim/common/cgen-scache.c.

brgds, H-P


  parent reply	other threads:[~2010-04-22  1:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 20:49 Mike Frysinger
2010-04-21 22:36 ` Doug Evans
2010-04-22  0:26   ` Mike Frysinger
2010-04-22  0:39     ` Mike Frysinger
2010-04-22  1:36       ` Doug Evans
2010-04-22  1:49       ` Hans-Peter Nilsson [this message]
2010-04-22  2:17         ` Mike Frysinger
2010-04-22  2:45           ` 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=alpine.BSF.2.00.1004212143050.79451@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --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