From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
davem@davemloft.net, riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement
Date: Fri, 19 Aug 2005 09:04:56 -0400 [thread overview]
Message-ID: <200508191304.j7JD4utA010195@laptop11.inf.utfsm.cl> (raw)
In-Reply-To: Message from Rusty Russell <rusty@rustcorp.com.au> of "Fri, 19 Aug 2005 17:27:06 +1000." <1124436426.23757.5.camel@localhost.localdomain>
Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Fri, 2005-08-19 at 00:10 -0700, Andrew Morton wrote:
> > Rusty Russell <rusty@rustcorp.com.au> wrote:
> > > I believe we just ignored sparc64. That usually works for solving these
> > > kind of bugs. 8)
> >
> > heh. iirc, it was demonstrable on x86 also.
>
> No. gcc-2.95 on Sparc64 put uninititialized vars into the bss, ignoring
> the __attribute__((section(".data.percpu"))) directive. x86 certainly
> doesn't have this, I just tested it w/2.95.
>
> Really, it's Sparc64 + gcc-2.95. Send an urgent telegram to the user
> telling them to upgrade.
I recently asked if gcc-2.95 was really still supported, and was told that
it is in common use for its speed...
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-08-19 13:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 20:02 [PATCH/RFT 0/5] " Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 1/5] " Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 2/5] " Rik van Riel
2005-08-10 20:27 ` David S. Miller, Rik van Riel
2005-08-10 20:38 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 3/5] " Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 4/5] " Rik van Riel
2005-08-10 20:31 ` David S. Miller, Rik van Riel
2005-08-18 0:38 ` Andrew Morton
2005-08-18 2:48 ` David S. Miller, Andrew Morton
2005-08-18 4:05 ` Andrew Morton
2005-08-18 4:48 ` David S. Miller, Andrew Morton
2005-08-19 7:03 ` Rusty Russell
2005-08-19 7:10 ` Andrew Morton
2005-08-19 7:27 ` Rusty Russell
2005-08-19 13:04 ` Horst von Brand [this message]
2005-08-10 23:22 ` Marcelo Tosatti
2005-08-11 0:06 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 5/5] " Rik van Riel
2005-08-11 22:08 ` Song Jiang
2005-08-12 1:22 ` Rik van Riel
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=200508191304.j7JD4utA010195@laptop11.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=rusty@rustcorp.com.au \
/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