Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: tromey@redhat.com (Tom Tromey),
	gdb-patches@sourceware.org,
	       brobecker@adacore.com (Joel Brobecker),
	       alves.ped@gmail.com (Pedro Alves)
Subject: Re: [patch+7.4] reread.exp 7.3->7.4 regression
Date: Mon, 19 Dec 2011 21:49:00 -0000	[thread overview]
Message-ID: <201112192137.pBJLb4UZ026021@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20111219191201.GA7401@host2.jankratochvil.net> from "Jan Kratochvil" at Dec 19, 2011 08:12:01 PM

Jan Kratochvil wrote:
> On Mon, 19 Dec 2011 11:30:54 +0100, Ulrich Weigand wrote:
> > I can test on ARM if you want.
> 
> I have tested it on fedora13beta.  Just on
> 
> Hardware        : OMAP3 Beagle Board
> Revision        : 0020
> Processor       : ARMv7 Processor rev 2 (v7l)
> BogoMIPS        : 506.27
> 
> it takes 57m28.760s to build GDB (although with full symbols) and 51m13.889s
> to run the testsuite, is it normal to develop on ARM with this performance?

I guess so.  A Panda is a bit faster than the Beagle, but still ...

> > Your initial patch already moved the callbacks calls up a bit;
> 
> My patch was using free_objfile, I do not understand which patch of mine do
> you refer to now.
> 	Re: [patch] Replace reread_symbols by load+free calls
> 	http://sourceware.org/ml/gdb-patches/2009-06/msg00696.html

Sorry, I was refering to the first patch in list you had in the mail I replied to.
Specifically, I was talking about this patch:
http://sourceware.org/ml/gdb-patches/2009-06/msg00606.html
which seems to have gone upstream 2009-06-23.

> > In addition, we should probably call observer_notify_new_objfile so that new
> > tables can be built up for the re-read file ...
> 
> I can post it afterwards, that is probably not for 7.4, I will have to run the
> ARM testsuite again.

OK, thanks.

> No regressions on {x86_64,x86_64-m32,i686}-fedora16-linux-gnu and on
> arm-fedora13beta-linux-gnu.  OK to check it in and for 7.4?
> 
> gdb/
> 2011-12-19  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* symfile.c (reread_symbols): Move free_objfile_separate_debug,
> 	preserve_values, sym_finish and clear_objfile_data calls before BFD
> 	close.  Move free_objfile_separate_debug as the very first call.  New
> 	comment on the ordering.

This looks reasonable to me, and seems preferable to the ARM-specific hack ...


Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2011-12-19 21:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 12:00 Jan Kratochvil
2011-12-19  4:17 ` Joel Brobecker
2011-12-19  9:54   ` Jan Kratochvil
2011-12-19 10:13     ` Joel Brobecker
2011-12-19 10:31       ` Jan Kratochvil
2011-12-19 10:32 ` Ulrich Weigand
2011-12-19 19:05   ` Tom Tromey
2011-12-19 19:12     ` Jan Kratochvil
2011-12-19 20:02       ` Tom Tromey
2011-12-19 19:47   ` Jan Kratochvil
2011-12-19 21:49     ` Ulrich Weigand [this message]
2011-12-19 22:56       ` [commit+7.4] " Jan Kratochvil
2011-12-21 11:46   ` [patch] reread_symbols observer_notify_new_objfile - fix ARM unwinding after reread [Re: [patch+7.4] reread.exp 7.3->7.4 regression] Jan Kratochvil
2011-12-21 13:13     ` [patch] reread_symbols observer_notify_new_objfile - fix ARM unwinding after reread [Re: [patch+7.4] reread.exp 7.3->7.4 regres Ulrich Weigand
2011-12-21 14:27       ` [commit] [patch] reread_symbols observer_notify_new_objfile - fix ARM unwinding after reread Jan Kratochvil
2011-12-19 15:28 ` [patch+7.4] reread.exp 7.3->7.4 regression Tom Tromey

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=201112192137.pBJLb4UZ026021@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=alves.ped@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@redhat.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