From: Holger Bettag <hobold@informatik.uni-bremen.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: RE: Using in_8 and out_8 without module optimization
Date: Tue, 21 Oct 2003 16:03:33 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.53.0310211558320.16885@bob.informatik.uni-bremen.de> (raw)
In-Reply-To: <3F710B1D000A0C08@mssbzhh-int.msg.bluewin.ch>
On Tue, 21 Oct 2003, Wolfgang Grandegger wrote:
> To ensure that the asm-code is executed in sequence with your
> C-code use:
>
> -fno-schedule-insns -fno-schedule-insns2
>
Some other optimizations might still rearrange code, so consider
-fno-strength-reduce and -fno-move-all-moveables and possibly a few other
switches. Just compile with -S and see if the assembly code looks right.
I think there is also a switch to force inline functions to be
instantiated, could be -fno-inline or -fforce-no-inline, but the former
solution is likely a lot better.
Holger
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-21 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 13:25 Using in_8 and out_8 without module optimization Seb James
2003-10-21 13:48 ` Wolfgang Grandegger
2003-10-21 14:03 ` Holger Bettag [this message]
2003-10-22 15:41 ` linas
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=Pine.GSO.4.53.0310211558320.16885@bob.informatik.uni-bremen.de \
--to=hobold@informatik.uni-bremen.de \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).