All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: gcc 2v optimization problem with C++ exceptions?
Date: Tue, 10 Apr 2001 17:14:06 -0400	[thread overview]
Message-ID: <01041017140600.09487@localhost> (raw)
In-Reply-To: <200104102051.QAA20310@makai.watson.ibm.com>


Hi,

On Tuesday 10 April 2001 16:51, David Edelsohn wrote:
> I am confused why the disassembly contains values like 0x78364e55
> and 0x78664476 because those seem like 64-bit PowrePC instructions.
>
> David

Please ignore the dissassembly (as I mentioned in my e-mail).  The objdump -D
will try to disassemble everything including the __EXCEPTION__TABLE__ entries.

The table entries (i.e. data) are what was different, they are not
instructions AFAIK.

Kevin


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-04-10 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 17:19 gcc 2v optimization problem with C++ exceptions? Kevin B. Hendricks
2001-04-10 20:51 ` David Edelsohn
2001-04-10 21:14   ` Kevin B. Hendricks [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=01041017140600.09487@localhost \
    --to=khendricks@ivey.uwo.ca \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=dje@watson.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.