From: Andrew Cagney <ac131313@cygnus.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Bugfixes on x86-64 target
Date: Tue, 26 Feb 2002 18:49:00 -0000 [thread overview]
Message-ID: <3C7C492D.50605@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202261827510.21868-100000@chimera.suse.cz>
> Index: ChangeLog
> from Michal Ludvig <mludvig@suse.cz>
>
> * x86-64-tdep.c (value.h): Delete.
> (gdb_assert.h): Include.
> (x86_64_register_convert_to_virtual,
> x86_64_register_convert_to_raw ): Add check which lets only
> floating-point values to be converted.
> (value_push): Delete.
> (x86_64_push_arguments): Order of arguments pushed on stack fixed.
> (i386_gdbarch_init): Number of register_bytes fixed.
>
Nice! I've checked it in (I've also re-indented the file as a separate
commit).
Andrew
next prev parent reply other threads:[~2002-02-27 2:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 9:28 Michal Ludvig
2002-02-26 18:49 ` Andrew Cagney [this message]
2002-03-01 7:00 ` Andrew Cagney
2002-03-04 3:07 ` Michal Ludvig
2002-03-04 18:27 ` Andrew Cagney
2002-03-05 4:51 ` Michal Ludvig
2002-03-05 6:55 ` Andrew Cagney
2002-03-05 8:27 ` Michal Ludvig
2002-03-05 11:14 ` Andrew Cagney
2002-02-26 9:50 Michal Ludvig
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=3C7C492D.50605@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@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