From: Derek Homeier <supas100@astrophysik.uni-kiel.de>
To: linuxppc-dev@lists.linuxppc.org
Cc: Michael Norton <mnorton@cisco.com>
Subject: Re: COPTS for Makefile LinuxPPC 2000
Date: Mon, 23 Oct 2000 13:39:29 +0200 (MET DST) [thread overview]
Message-ID: <Pine.SOL.3.95.1001023131438.18258B-100000@juliet> (raw)
In-Reply-To: <200010210500.AAA23065@lists.linuxppc.org>
On Fri, 20 Oct 2000 15:17:26 -0700 (PDT), Michael Norton <mnorton@cisco.com> wrote:
>
> I am trying to build the OpenGL Heretic game and there are compiler options in t
> he Makefile for m68k but not for the PPC.
>
> COPT.m68k = -m68020-60 -O2 -fomit-frame-pointer -D__BIG_ENDIAN__ -D__32BIT__ \
> -DHAVE_ALLOCA_H
>
>
> was should this statement read if I am going to compile a PPC image on my G4?
>
Well, you probably should keep the defines, and possibly the "-fomit-frame-pointer"
as well, so leave everything after that unchanged. It's possible you need
"-fsigned-char" in addition. You obviously wouldn't want the "-m68020-60"
which turns on m68k-specific tuning. You might simply try "-O2" or "-O3" for a
first run. There also are some architecture-specific flags available on PPC,
such as"-mcpu=604", don't know if there is a flag for 750 or even 7400 yet.
You should look at the gcc info page for more details on the different
optimizations (under "Invoking GCC::"). Chances are you won't need
terribly agressive optimization if that game actually runs on a 68k :-).
HTH,
Derek
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-10-23 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200010210500.AAA23065@lists.linuxppc.org>
2000-10-23 11:39 ` Derek Homeier [this message]
2000-10-23 15:35 ` COPTS for Makefile LinuxPPC 2000 William Blew
2000-10-23 17:38 ` gpm and XF401 (Re: ADB-Mouse) Derek Homeier
2000-10-23 12:55 ` Henning Lvser
2000-10-23 13:00 ` Olaf Hering
2000-10-23 13:06 ` Henning Lvser
2000-10-23 15:40 ` William Blew
2000-10-23 16:27 ` Josh Huber
2000-10-23 18:03 ` Geert Uytterhoeven
2000-10-20 22:17 COPTS for Makefile LinuxPPC 2000 Michael Norton
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.SOL.3.95.1001023131438.18258B-100000@juliet \
--to=supas100@astrophysik.uni-kiel.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mnorton@cisco.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;
as well as URLs for NNTP newsgroup(s).