Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, luisgpm@linux.vnet.ibm.com
Subject: Re: [RFC] PPC: Skip call to __eabi in main()
Date: Thu, 07 Aug 2008 14:04:00 -0000	[thread overview]
Message-ID: <20080807140339.GA12607@caradoc.them.org> (raw)
In-Reply-To: <20080806174037.7cfe6445@mesquite.lan>

On Wed, Aug 06, 2008 at 05:40:37PM -0700, Kevin Buettner wrote:
> With regard to my patch, I'd prefer to commit it in its present form
> and then address improvements to PowerPC instruction decoding at a
> later time.  I considered using my preferred approach when I adjusted
> my patch, but decided against doing so because a different approach
> (that of using explicit masks and comparisons) was already in use.

I think this is reasonable.

> FWIW, this isn't the only approach that I find compelling.  I recently
> worked on a port which utilizes the instruction decoder in opcodes/. 
> This decoder is also used for the disassembler and simulator.  It
> completely decodes the instruction, returning a symbolic (via enums)
> opcodes, and completely decoded instruction offsets, registers, etc.

I wish other ports provided enough detail in libopcodes to do this!
It's an excellent approach.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-07 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 22:54 Kevin Buettner
2008-07-22  4:45 ` Thiago Jung Bauermann
2008-07-23  1:13   ` Kevin Buettner
2008-07-29  0:22     ` Kevin Buettner
2008-08-01 18:46       ` Luis Machado
2008-08-07  0:42         ` Kevin Buettner
2008-08-07 14:04           ` Daniel Jacobowitz [this message]
2008-08-07 15:14             ` Luis Machado
2008-08-12  0:30       ` Kevin Buettner

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=20080807140339.GA12607@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=luisgpm@linux.vnet.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