Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [rfc]: Use trad_frame_alloc_saved_regs  in alpha-tdep
Date: Mon, 18 Feb 2008 20:03:00 -0000	[thread overview]
Message-ID: <47B9E3E4.7050804@de.ibm.com> (raw)
In-Reply-To: <200802181935.m1IJZaBG010057@brahms.sibelius.xs4all.nl>

Mark Kettenis schrieb:
>> Date: Wed, 13 Feb 2008 08:46:27 +0100
>> From: Markus Deuling <deuling@de.ibm.com>
>>
>> This patch makes alpha-tdep use trad_frame_alloc_saved_regs. I'd
>> appreciate it very much if someone with access to an alpha machine
>> could run the testsuite.
> 
> This causes significant regressions on OpenBSD/alpha.  I'll see if I
> can figure out what's going wrong later this week.
> 
>> ChangeLog:
>>
>> 	* alpha-tdep.c (alpha_heuristic_unwind_cache): Replace saved_regs by
>> 	trad_frame_saved_reg. Remove return_reg.
>> 	(trad-frame.h): New include. 
>> 	(alpha_heuristic_frame_unwind_cache): Use trad_frame_alloc_saved_regs
>> 	instead of frame_obstack_zalloc. 
>> 	(alpha_heuristic_frame_prev_register): Use trad_frame_get_prev_register.
>>
>> 	* Makefile.in (alpha-tdep.o): Add dependency to trad_frame_h. 
> 


Hi Mark,

thank you very much for your effort. Maybe you can provide me your gdb.log file from this testrun?


-- 
  Markus Deuling
  GNU Toolchain for Linux on Cell BE
  deuling@de.ibm.com


  reply	other threads:[~2008-02-18 20:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  7:48 Markus Deuling
2008-02-15 21:43 ` Joel Brobecker
2008-02-15 23:22   ` Mark Kettenis
2008-02-18 14:15     ` Markus Deuling
2008-02-18 14:57       ` Mark Kettenis
2008-02-18 19:36 ` Mark Kettenis
2008-02-18 20:03   ` Markus Deuling [this message]
2008-02-19 21:18     ` Mark Kettenis
2008-02-20 15:47       ` Markus Deuling

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=47B9E3E4.7050804@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=uweigand@de.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