From: "H . J . Lu" <hjl@lucon.org>
To: Vivien Chappelier <vivien.chappelier@enst-bretagne.fr>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: binutils bug workaround
Date: Thu, 3 Jan 2002 13:53:34 -0800 [thread overview]
Message-ID: <20020103135334.A3978@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0201032241030.8906-200000@melkor>; from vivien.chappelier@enst-bretagne.fr on Thu, Jan 03, 2002 at 10:44:30PM +0100
On Thu, Jan 03, 2002 at 10:44:30PM +0100, Vivien Chappelier wrote:
> Hi,
>
> There is a binutils bug (as) which produces bad addresses when
> getting the address of a struct member for initializing the same struct,
> and when there is data or static functions declared before:
> int test = 0xdeadbeef;
>
> struct {
> int dummy;
> void *ptr;
> } bug =
> {
> ptr: &bug.ptr
> };
>
> will produce bad value for bug.ptr.
>
> This patch move the declaration of kswapd_wait as a workaround to
> this compiler bug. This probably affects all mips64 kernels.
>
Shouldn't you fix the assmbler instead?
H.J.
next prev parent reply other threads:[~2002-01-03 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 21:44 binutils bug workaround Vivien Chappelier
2002-01-03 21:53 ` H . J . Lu [this message]
2002-01-03 21:56 ` Ralf Baechle
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=20020103135334.A3978@lucon.org \
--to=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
--cc=vivien.chappelier@enst-bretagne.fr \
/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