Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT]: Follow-up ia64 patch for --without-libunwind
Date: Fri, 10 Jun 2005 15:32:00 -0000	[thread overview]
Message-ID: <42A9B26C.7040407@redhat.com> (raw)
In-Reply-To: <20050610034652.GA23889@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Thu, Jun 09, 2005 at 09:15:31PM -0400, jjohnstn wrote:
> 
>>The following patch fixes the problem with building the latest
>>ia64-tdep.c with --without-libunwind configured.  It also removes
>>warnings about gdb_byte vs void *.
>>
>>2005-06-09  Jeff Johnston  <jjohnstn@redhat.com>
>>                                                                                
>>        * ia64-tdep.c (ia64_pseudo_register_read): Use gdb_byte and
>>        protect libunwind references with HAVE_LIBUNWIND_IA64_H flag.
>>        * (ia64_pseudo_register_write): Use gdb_byte to remove warning.
>>        * (ia64_register_to_value, ia64_value_to_register): Ditto.
>>        * (ia64_frame_prev_register): Ditto.
>>        * (ia64_libunwind_frame_prev_register): Ditto.
>>        * (ia64_sigtramp_frame_prev_register): Ditto.
>>        * (ia64_libunwind_sigtramp_frame_prev_register): Ditto.
>>        * (ia64_store_return_value): Ditto.
> 
> 
> Please fix the formatting - all but the first leading "*" are
> unnecessary.
> 
>

D'oh.  I've done enough ChangeLog entries to know that.  Total brain freeze. :( 
  Fixed.

-- Jeff J.


      reply	other threads:[~2005-06-10 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10  1:15 jjohnstn
2005-06-10  3:46 ` Daniel Jacobowitz
2005-06-10 15:32   ` Jeff Johnston [this message]

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=42A9B26C.7040407@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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