From: Ralf Baechle <ralf@linux-mips.org>
To: Maxime Bizon <mbizon@freebox.fr>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Kernel freezes in r4k_flush_icache_range() with CONFIG_CPU_MIPS32_R2
Date: Thu, 22 Dec 2005 12:10:23 +0100 [thread overview]
Message-ID: <20051222111023.GD1918@linux-mips.org> (raw)
In-Reply-To: <1135218691.9874.186.camel@sakura.staff.proxad.net>
On Thu, Dec 22, 2005 at 03:31:31AM +0100, Maxime Bizon wrote:
> > FYI, GCC 3.4.4 produces the following code which is clearly wrong:
>
> > Please file a bug report at: "http://gcc.gnu.org/bugzilla/".
>
> Same with 3.3 and 3.2...
>
> I'm really not familiar with inline assembly so I would appreciate that
> any gcc guru here confirm instruction_hazard() code is correct before I
> (or he) submit the bug report.
>
> As the bug seems to be in all gcc versions, I guess we should find a
> workaround... I changed the code to use an asm label instead of the C
> label and the bug disappeared. But I'm not sure my changes are correct
> for any platform other than mine...
We ran into similar problems in the past. It only seems to be a matter
of the code nearby and the exact options to trigger it.
The alternative is manually loading the address using la / dla which
defeats gcc's splitting of address loading. And having to use different
code for 32-bit and 64-bit sucks.
> Could anyone with the right skills help me to write a valid workaround
> please ?
>
> Here is what I have:
>
> __asm__ __volatile__(
> "lui $2,1f\n"
> "addiu $2,1f\n"
> "jr.hb $2\n1:":: );
Wrong, breaks 64-bit and uses $2 without telling gcc about it.
Ralf
prev parent reply other threads:[~2005-12-22 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 2:57 Kernel freezes in r4k_flush_icache_range() with CONFIG_CPU_MIPS32_R2 Maxime Bizon
2005-12-20 11:47 ` Maciej W. Rozycki
2005-12-22 2:31 ` Maxime Bizon
2005-12-22 11:10 ` Ralf Baechle [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=20051222111023.GD1918@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=mbizon@freebox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.