virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: For discussion of SYSLINUX and tftp-hpa <syslinux@zytor.com>
Cc: Andi Kleen <ak@suse.de>, Sahil Rihan <srihan@vmware.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: [syslinux] Vmware crashes if compress/misc.c scrolls?
Date: Sat, 04 Aug 2007 13:14:15 -0700	[thread overview]
Message-ID: <46B4DE17.7070108@zytor.com> (raw)
In-Reply-To: <46B48ADF.9050006@vmware.com>

Zachary Amsden wrote:
> 
> It was 2.6.21.4, so it is fairly recent, but with 32-bit decompress 
> stage.  GCC was 4.2.0.
> 
> Sounds like a gcc bug, to me.
> 

I would argue that anything that causes a function and its callsite to
diverge, when they're part of the same file, is a gcc bug almost by
definition.

That doesn't mean it's not a problem and that there is not a solution --
if nothing else there should be a patch for -stable.

	-hpa

      reply	other threads:[~2007-08-04 20:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 23:44 Vmware crashes if compress/misc.c scrolls? H. Peter Anvin
2007-06-21  0:07 ` Jeremy Fitzhardinge
2007-06-21  0:17   ` H. Peter Anvin
2007-06-21  0:21     ` Jeremy Fitzhardinge
2007-06-21  0:25       ` H. Peter Anvin
2007-06-21  0:27         ` Jeremy Fitzhardinge
2007-06-21  0:46           ` H. Peter Anvin
2007-06-21 21:54             ` Zachary Amsden
2007-06-22  2:22               ` H. Peter Anvin
2007-06-22  2:34                 ` Zachary Amsden
2007-06-22  3:09                   ` Jeremy Fitzhardinge
2007-08-04  4:48 ` Zachary Amsden
2007-08-04  9:24   ` Andi Kleen
2007-08-04 12:08     ` Zachary Amsden
2007-08-04 14:19     ` Zachary Amsden
2007-08-04 20:14       ` H. Peter Anvin [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=46B4DE17.7070108@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srihan@vmware.com \
    --cc=syslinux@zytor.com \
    --cc=virtualization@lists.osdl.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).