From: Zhang Fuxin <fxzhang@ict.ac.cn>
To: Richard Hodges <rh@matriplex.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Ranjan Parthasarathy <ranjanp@efi.com>,
"'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Disabling lwl and lwr instruction generation
Date: Thu, 13 Mar 2003 10:07:46 -0500 [thread overview]
Message-ID: <3E709EC2.7050501@ict.ac.cn> (raw)
In-Reply-To: Pine.BSF.4.50.0303121647400.95890-100000@mail.matriplex.com
Richard Hodges wrote:
>On Thu, 13 Mar 2003, Ralf Baechle wrote:
>
>
>
>>On Wed, Mar 12, 2003 at 10:05:20AM -0800, Ranjan Parthasarathy wrote:
>>
>>
>>
>>>Is there a way to tell gcc to not generate the lwl, lwr instructions?
>>>
>>>
>>Gcc will only ever generate these instructions when __attribute__((unaligned))
>>is used.
>>
>>
>
>I got lwl and lwr from a memcpy() with two void pointers...
>
>I quickly changed those to the (aligned) structure pointers instead, and
>then memcpy() changed to ordinary word loads and stores.
>
>So, is somebody starting a toolchain for that new Chinese CPU? :-)
>
>
I don't hear about it,but it will happen soon or later:)
We work around lwl/lwr problem by modifying toolchain from H.J. Lu's rh
port.
it seems that gcc will explicitly output lwl/lwr for unaligned block
copy,in other cases it will generate
ulW macros for gas to handle.
>-Richard
>
>
>
>
>
next prev parent reply other threads:[~2003-03-13 2:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 18:05 Disabling lwl and lwr instruction generation Ranjan Parthasarathy
2003-03-13 0:43 ` Ralf Baechle
2003-03-13 0:50 ` Richard Hodges
2003-03-13 1:33 ` Ralf Baechle
2003-03-13 15:07 ` Zhang Fuxin [this message]
2003-03-13 0:52 ` Thiemo Seufer
2003-03-13 1:18 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 18:00 Ranjan Parthasarathy
2003-03-13 18:00 ` Ranjan Parthasarathy
2003-03-13 18:09 Ranjan Parthasarathy
2003-03-13 18:09 ` Ranjan Parthasarathy
2003-03-13 21:35 ` Ralf Baechle
2003-03-14 0:21 ` Alan Cox
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=3E709EC2.7050501@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=ranjanp@efi.com \
--cc=rh@matriplex.com \
/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