From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: 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 02:18:55 +0100 [thread overview]
Message-ID: <20030313021855.A7940@linux-mips.org> (raw)
In-Reply-To: <20030313005203.GH13122@rembrandt.csv.ica.uni-stuttgart.de>; from ica2_ts@csv.ica.uni-stuttgart.de on Thu, Mar 13, 2003 at 01:52:03AM +0100
On Thu, Mar 13, 2003 at 01:52:03AM +0100, Thiemo Seufer 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.
>
> Which might be not that obvious, e.g. __attribute__((packed)) can cause such
> instructions, too.
Typo - I meant __attribute__((packed)). There is no such thing as
__attribute__((unaligned)).
Ralf
next prev parent reply other threads:[~2003-03-13 1:19 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
2003-03-13 0:52 ` Thiemo Seufer
2003-03-13 1:18 ` Ralf Baechle [this message]
-- 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=20030313021855.A7940@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.org \
--cc=ranjanp@efi.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