Process Specific Code Generation

From what I’ve read, it’s “highly recommended” that I use “cc” or “qcc” to
compile my programs. If I were to do so, how do I specify which type of CPU
I’d like to optimize for? It seems silly to optimize for the default 386 CPU
when I’m running dual PIII’s…

What exactly are the tradeoffs involved with using cc/qcc or gcc?

-Warren

That’s supposed to be “Processor Specific”… Dang fingers!


“Warren Peece” <warren@nospam.com> wrote in message
news:8vc474$66r$1@inn.qnx.com
| From what I’ve read, it’s “highly recommended” that I use “cc” or “qcc” to
| compile my programs. If I were to do so, how do I specify which type of CPU
| I’d like to optimize for? It seems silly to optimize for the default 386 CPU
| when I’m running dual PIII’s…
|
| What exactly are the tradeoffs involved with using cc/qcc or gcc?
|
| -Warren
|
|
|

You can pass through any options with the pass through command.

eg

$ qcc -Wc,-mcpu=pentium -O2 -c file.c

or

$ qcc -Wc,-march=pentium -O2 -c file.c

What’s the difference? The first optimises for Pentium timings, whereas
the second will actually use Pentium specific instructions, without trying
to maintain 386 compatibility.

GCC 2.95.2 supports the following processor types:

i386
i486
i586 or pentium
i686 or pentiumpro
k6

Note that yet more optimiser bugs may show up if you do this… :v)

Also note that the latest development branch of GCC (soon to be
released as GCC 3.0) adds athlon support.

Warren Peece <warren@nospam.com> wrote:

From what I’ve read, it’s “highly recommended” that I use “cc” or “qcc” to
compile my programs. If I were to do so, how do I specify which type of CPU
I’d like to optimize for? It seems silly to optimize for the default 386 CPU
when I’m running dual PIII’s…

What exactly are the tradeoffs involved with using cc/qcc or gcc?

-Warren


cburgess@qnx.com

It’s a beautiful thing… Thanks!

-Warren


<cburgess@qnx.com> wrote in message news:8vc6b6$3i6$1@nntp.qnx.com
| You can pass through any options with the pass through command.
|
| eg
|
| $ qcc -Wc,-mcpu=pentium -O2 -c file.c
|
| or
|
| $ qcc -Wc,-march=pentium -O2 -c file.c
|
| What’s the difference? The first optimises for Pentium timings, whereas
| the second will actually use Pentium specific instructions, without trying
| to maintain 386 compatibility.
|
| GCC 2.95.2 supports the following processor types:
|
| i386
| i486
| i586 or pentium
| i686 or pentiumpro
| k6
|
| Note that yet more optimiser bugs may show up if you do this… :v)
|
| Also note that the latest development branch of GCC (soon to be
| released as GCC 3.0) adds athlon support.
|
| Warren Peece <warren@nospam.com> wrote:
| > From what I’ve read, it’s “highly recommended” that I use “cc” or “qcc” to
| > compile my programs. If I were to do so, how do I specify which type of
CPU
| > I’d like to optimize for? It seems silly to optimize for the default 386
CPU
| > when I’m running dual PIII’s…
|
| > What exactly are the tradeoffs involved with using cc/qcc or gcc?
|
| > -Warren
|
|
|