From: "J. Johnston" <jjohnstn@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] more structs.exp kfails
Date: Thu, 04 Dec 2003 21:46:00 -0000 [thread overview]
Message-ID: <3FCFAB3B.8030609@redhat.com> (raw)
In-Reply-To: <3FCF727F.6030807@redhat.com>
Andrew Cagney wrote:
>
> The attatched tweaks structs.exp so that it KFAILs the case where a
> "return struct" fails because the target hasn't implemented the relevant
> code.
>
> Jeff and I were puzzling over an apparent regression in the ia64 - this
> better clasifies it as something that is known to have never worked.
>
> So, jeff, if it works for you, I'll commit it in a day or so,
> Andrew
The patch works but it uncovers two separate bugs. 1. printing long doubles on
the ia64 is hosed 2. once fixing printing long doubles, doing a p/c on a long
double value causes it to spit out the hex bytes of the long double
That doesn't affect whether you should check this in. I will shortly post a fix
for the ia64-tdep file.
-- Jeff J.
next prev parent reply other threads:[~2003-12-04 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 17:44 Andrew Cagney
2003-12-04 21:46 ` J. Johnston [this message]
2003-12-06 22:47 ` Andrew Cagney
2003-12-04 18:02 Michael Elizabeth Chastain
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=3FCFAB3B.8030609@redhat.com \
--to=jjohnstn@redhat.com \
--cc=ac131313@redhat.com \
--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