public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Bo Thorsen <bo@sonofthor.dk>,
	bugs@x86-64.org, gcc@gcc.gnu.org, Jan Hubicka <jh@suse.cz>
Subject: Re: Exception handling problem on x86-64
Date: Thu, 25 Apr 2002 10:33:00 -0000	[thread overview]
Message-ID: <20020425101618.B2336@redhat.com> (raw)
In-Reply-To: <200204251707.NAA25352@makai.watson.ibm.com>; from dje@watson.ibm.com on Thu, Apr 25, 2002 at 01:07:15PM -0400

On Thu, Apr 25, 2002 at 01:07:15PM -0400, David Edelsohn wrote:
> 	Is this possibly related to the exception unwinding bug affecting
> Mips that Ed Maste reported in February?

No.  x86-64 does not have the same 32-bit value in 64-bit 
register problem.


r~

      reply	other threads:[~2002-04-25 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07  8:50 Exception unwinding bug Ed Maste
2002-04-25  2:55 ` Exception handling problem on x86-64 Bo Thorsen
2002-04-25 10:08   ` David Edelsohn
2002-04-25 10:33     ` Richard Henderson [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=20020425101618.B2336@redhat.com \
    --to=rth@redhat.com \
    --cc=bo@sonofthor.dk \
    --cc=bugs@x86-64.org \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).