From: William Lee Irwin III <wli@holomorphy.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.7 build breakage around blkpg.c
Date: Fri, 29 Mar 2002 16:18:59 -0800 [thread overview]
Message-ID: <20020330001859.GA21206@holomorphy.com> (raw)
In-Reply-To: <20020328035926.GA10467@holomorphy.com> <20020329223501.GC9974@elf.ucw.cz>
At some point in the past, I wrote:
>> What hit me?
On Fri, Mar 29, 2002 at 11:35:02PM +0100, Pavel Machek wrote:
> gcc bug hit you. Workaround by adding volatile's to all local
> variables in affected function.
>From some other responses I got it was made clear to me that this
seems to do with generating an illegal instruction in response to
high register pressure around inline assembly.
Cheers,
Bill
prev parent reply other threads:[~2002-03-30 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 3:59 2.5.7 build breakage around blkpg.c William Lee Irwin III
2002-03-29 22:35 ` Pavel Machek
2002-03-30 0:18 ` William Lee Irwin III [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=20020330001859.GA21206@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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