Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] PPC: Skip call to __eabi in main()
Date: Fri, 01 Aug 2008 18:46:00 -0000	[thread overview]
Message-ID: <1217616315.29334.44.camel@gargoyle> (raw)
In-Reply-To: <20080728172221.3dc3764e@mesquite.lan>

Hi Kevin,

Sorry it took a while to reply.

On Mon, 2008-07-28 at 17:22 -0700, Kevin Buettner wrote:
> +#define BL_MASK 0xfc000001

We have a very similar mask used for displaced stepping called
BRANCH_MASK (0xfc000000). It doesn't care about the LK bit though, its
purpose is just to check for a generic branch instruction.

Maybe we should rename BL_MASK to something else incorporating the
notion that we expect a LK bit? Or maybe doing the check for the LK bit
manually in the code and using BL_MASK as is.

> +#define BL_INSTRUCTION 0x48000001

Similarly, we also have B_INSN (0x48000000), lacking the LK bit.

> +#define BL_DISPLACEMENT_MASK 0x03fffffc

Should we make the naming more generic (B_LI_MASK maybe?) as the
displacement field is common to a variety of I-form branch instructions?
Just a suggestion, doesn't need to change if you don't feel it clarifies
things.

Regards,
Luis


  reply	other threads:[~2008-08-01 18:46 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 [this message]
2008-08-07  0:42         ` Kevin Buettner
2008-08-07 14:04           ` Daniel Jacobowitz
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=1217616315.29334.44.camel@gargoyle \
    --to=luisgpm@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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