Message-Id:	<199906230757.JAA16919@mail2.it.kth.se>
X-Mailer:	exmh version 2.0.3 2/24/98
To:	pgcc AT delorie DOT com
From:	Janne Johansson <jj AT it DOT kth DOT se>
X-url:	http://www.it.kth.se/~jj/
Subject:	Re: pgcc does better, reboot, then does terrible!(SOLVED)
In-reply-to:	<376FCBCF.DC1921CB@uiuc.edu>
Mime-Version:	1.0
Date:	Wed, 23 Jun 1999 09:57:19 +0200
Sender:	jj AT it DOT kth DOT se
Reply-To:	pgcc AT delorie DOT com
X-Mailing-List:	pgcc AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> As to -mpentium.  I'm not sure how -m, -mcpu, -march are different.
> 
> For example, the kernel compiles with -m486 -DCPU=686 (or something like
> that), with your CPU set to 686.  Why not use -mpentium at least??

The -m<something> tells the compiler to act differently or use instructions 
and optimizations for the architecture that you specified, while the 
-Dsomething_else is a #define that affects the source, and makes the source 
act in different ways.

Just because the -D happens to define a constant that has the name "686" 
doesn't mean anything, it could as easily be -Dmight_have_large_L2_cache,
-Dhas_variable_mmu_table_size, -Dimpress_users or whatever.

See the difference?

-- 
"Backwards compatible" means: "if it isn't backwards, it's not compatible."

Http://www.it.kth.se/~jj

- Raw text -