From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc32 CVS broken
Date: Tue, 2 Oct 2007 21:42:44 +0300 [thread overview]
Message-ID: <f43fc5580710021142n62b9bf1fve1eb72f2950f52b6@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580710021059m6b71dccwfe4e82fd8b3aa13d@mail.gmail.com>
On 10/2/07, Blue Swirl <blauwirbel@gmail.com> wrote:
> On 10/2/07, Robert Reif <reif@earthlink.net> wrote:
> > Sparc32 CVS exits after illegal instruction trap.
>
> I can confirm this. Let's see if git bisect is any good.
a0bd188b4800c8db855ac5dde6356280c80a28b2 is first bad commit
commit a0bd188b4800c8db855ac5dde6356280c80a28b2
Author: blueswir1 <blueswir1>
Date: Mon Sep 24 18:41:27 2007 +0000
Fix loading above 4G
:100644 100644 75cbdedda798110b60f8ed416666da8d24fc1589
fe2ef9ba9a45446e871d2135bb61cfbc7073d71b M elf_ops.h
Surprising result.
next prev parent reply other threads:[~2007-10-02 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 22:56 [Qemu-devel] sparc32 CVS broken Robert Reif
2007-10-02 17:59 ` Blue Swirl
2007-10-02 18:42 ` Blue Swirl [this message]
2007-10-02 19:17 ` Blue Swirl
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=f43fc5580710021142n62b9bf1fve1eb72f2950f52b6@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 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 NNTP newsgroup(s).