Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	gdb-patches@sourceware.org, 	brobecker@adacore.com
Subject: Re: Improve end check on rs6000 prologue analyzer
Date: Wed, 18 Oct 2006 14:18:00 -0000	[thread overview]
Message-ID: <20061018141804.GB7771@nevyn.them.org> (raw)
In-Reply-To: <4535BE8B.8000003@cn.ibm.com>

On Wed, Oct 18, 2006 at 01:41:31PM +0800, Wu Zhou wrote:
> It seems that powerpc-linux is skipped as a whole:
> 
> if {[istarget *-*-aix*] || ![istarget "powerpc-*-*"]} then {
>     verbose "Skipping PowerPC prologue tests."
>     return
> }
> 
> What about open this for powerpc-linux?  I commented the above code and 
> have a test in both 32-bit and 64-bit mode on a ppc64 box.  For 32-bit 
> mode, there are six more PASS.  And for 64-bit mode, we have still 1 PASS 
> and 9 FAIL.  Why not just keep these FAIL there, to remind us that these 
> are places we need to improve?   Just my two cents anyway.  :-)

Thanks for catching this.  It's a bug in the patch: I was testing
in 32-bit mode on a powerpc64 system, so I removed the "64" from that
skip, but I forgot to put it back!  It should be skipping
powerpc64-*-*; the test won't work there because the asm isn't 64-bit
safe.

> I have yet another proposal to incorporate the bl_to_blrl patch, which is 
> discussed in http://sources.redhat.com/ml/gdb/2006-10/msg00085.html, into 
> this one.  Both are improvement for rs6000 prologue analyzer.

They're not related patches.  We'll deal with them separately.  I just
haven't had a chance to look at it yet, nor has anyone else, I suppose.


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-10-18 14:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 21:37 Daniel Jacobowitz
2006-09-30 19:32 ` Mark Kettenis
2006-09-30 20:25   ` Daniel Jacobowitz
2006-10-17 21:21   ` Daniel Jacobowitz
2006-10-17 22:15     ` Mark Kettenis
2006-10-18  5:41     ` Wu Zhou
2006-10-18 14:18       ` Daniel Jacobowitz [this message]
2006-10-18 19:58     ` Mark Kettenis
2006-10-18 20:06       ` Daniel Jacobowitz
2006-11-30 20:12         ` Daniel Jacobowitz
2007-02-15 20:20           ` Aman Wardak
2007-03-09 15:05       ` Daniel Jacobowitz
2007-03-11 19:13         ` Mark Kettenis
2007-03-12 12:19           ` Daniel Jacobowitz
2007-03-12 21:02             ` Mark Kettenis
2007-03-12 21:09               ` Daniel Jacobowitz
2007-03-12 23:05                 ` Mark Kettenis
2007-03-13  4:24                   ` Eli Zaretskii
2007-04-10 21:10                     ` Daniel Jacobowitz
2007-04-11  3:35                       ` Eli Zaretskii
2007-04-11 11:11                         ` Daniel Jacobowitz
2007-03-13 17:37                   ` Daniel Jacobowitz
2007-04-17  2:02         ` Andreas Schwab
2007-04-17 15:02           ` Daniel Jacobowitz

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=20061018141804.GB7771@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=woodzltc@cn.ibm.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