From: Mark Kettenis <kettenis@science.uva.nl>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] Fix x86 floating point vs. thread problem
Date: Wed, 12 Dec 2001 12:25:00 -0000 [thread overview]
Message-ID: <s3izo4ogpd7.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: Kevin Buettner's message of Thu, 6 Dec 2001 16:48:07 -0700
Kevin Buettner <kevinb@redhat.com> writes:
> * i387-nat.c (i387_fill_fxsave): Change type of ``val'' from char
> to short so that we don't memcpy() beyond the end of this buffer.
> Also, change shift value used in computing val to account for the
> fact that only eight bits are used.
Looks good. I'm not surprised there was a bug lurking here. Please
check this in. Thanks!
Mark
next prev parent reply other threads:[~2001-12-12 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 15:48 Kevin Buettner
2001-12-06 16:00 ` Daniel Jacobowitz
2001-12-06 16:27 ` Kevin Buettner
2001-12-12 12:25 ` Mark Kettenis [this message]
2001-12-13 9:38 ` Kevin Buettner
2001-12-13 15:48 ` Mark Kettenis
[not found] ` <kettenis@science.uva.nl>
2001-12-18 16:22 ` 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=s3izo4ogpd7.fsf@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=gdb-patches@sources.redhat.com \
--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