From: Peter Schmid <schmid@ltoi.iap.physik.tu-darmstadt.de>
To: egcs@cygnus.com
Subject: i386 of pentium architecture?
Date: Mon, 01 Dec 1997 07:38:00 -0000 [thread overview]
Message-ID: <Pine.A32.3.95.971201153053.22215A-100000@ltoi.iap.physik.tu-darmstadt.de> (raw)
Is an i386 considered to be of pentium architecture?
When egcs compiles a random programm e.g.
s.c
int main()
{
return 0;
}
the argument -march=pentium is set implicitly when cc1 runs.
The preprocessor options are correct.
gcc -v -o s s.c -save-temps
Reading specs from /usr/lib/gcc-lib/i386-pc-linux-gnulibc1/egcs-2.90.19/specs
gcc version egcs-2.90.19 971127 (gcc2-970802 experimental)
/usr/lib/gcc-lib/i386-pc-linux-gnulibc1/egcs-2.90.19/cpp -lang-c -v -undef -D__GNUC__=2 -D__GNUC_MINOR__=90 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem(posix) -Di386 -Asystem(unix) -Acpu(i386) -Amachine(i386) -D_
_i386__ -Asystem(unix) -Acpu(i386) -Amachine(i386) s.c s.i
GNU CPP version egcs-2.90.19 971127 (gcc2-970802 experimental) (i386 Linux/ELF)
s.s
/ options passed:
/ options enabled: -fpeephole -ffunction-cse -fkeep-static-consts
/ -fpcc-struct-return -fcommon -fverbose-asm -fgnu-linker -fargument-alias
/ -m80387 -mhard-float -mno-soft-float -mieee-fp -mfp-ret-in-387
/ -mschedule-prologue -mcpu=i386 -march=pentium
^^^^^^^^^^^^^
when I add -m386 to CFLAGS I get:
s.s
/ options passed: -mcpu=i386 -march=i386 -m386
/ options enabled: -fpeephole -ffunction-cse -fkeep-static-consts
/ -fpcc-struct-return -fcommon -fverbose-asm -fgnu-linker -fargument-alias
/ -m80387 -mhard-float -mno-soft-float -mieee-fp -mfp-ret-in-387
/ -mschedule-prologue -mcpu=i386 -march=i386
^^^^^^^^^^^
The contents of the specs file:
*asm:
%{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*} %{Wa,*:%*}
*asm_final:
%|
*cpp:
%(cpp_cpu) %[cpp_cpu] %{fPIC:-D__PIC__ -D__pic__} %{fpic:-D__PIC__ -D__pic__} %{posix:-D_POSIX_SOURCE}
*cc1:
%(cc1_cpu) %{profile:-p}
*cc1plus:
*endfile:
%{!shared:crtend.o%s} %{shared:crtendS.o%s} crtn.o%s
*link:
-m elf_i386 %{shared:-shared} %{!shared: %{!ibcs: %{!static: %{rdynamic:-export-dynamic} %{!dynamic-linker:-dynamic-linker /lib/ld-linux.so.1}} %{static:-static}}}
*lib:
%{!shared: %{p:-lgmon} %{pg:-lgmon} %{profile:-lgmon -lc_p} %{!profile:%{!ggdb:-lc} %{ggdb:-lg}}}
*libgcc:
-lgcc
*startfile:
%{!shared: %{pg:gcrt1.o%s} %{!pg:%{p:gcrt1.o%s} %{!p:%{profile:gcrt1.o%s} %{!profile:crt1.o%s}}}} crti.o%s %{!shared:crtbegin.o%s} %{shared:crtbeginS.o%s}
*switches_need_spaces:
*signed_char:
%{funsigned-char:-D__CHAR_UNSIGNED__}
*predefines:
-D__ELF__ -Dunix -Dlinux -Asystem(posix)
*cross_compile:
0
*version:
egcs-2.90.19
*multilib:
. ;
*multilib_defaults:
*multilib_extra:
*multilib_matches:
*cpp_cpu:
-Di386 -Asystem(unix) -Acpu(i386) -Amachine(i386) %{mcpu=i486:-Di486} %{m486:-Di486} %{mpentium:-Dpentium -Di586} %{mcpu=pentium:-Dpentium -Di586} %{mpentiumpro:-Dpentiumpro -Di686} %{mcpu=pentiumpro:-Dpentiumpro -Di686}
*cc1_cpu:
%{!mcpu*: %{m386:-mcpu=i386 -march=i386} %{mno-486:-mcpu=i386 -march=i386} %{m486:-mcpu=i486 -march=i486} %{mno-386:-mcpu=i486 -march=i486} %{mno-pentium:-mcpu=i486 -march=i486} %{mpentium:-mcpu=pentium} %{mno-pentiumpro:-mcpu=pentium} %{mpentiumpro:-mcpu
=pentiumpro}}
Peter Schmid
reply other threads:[~1997-12-01 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.A32.3.95.971201153053.22215A-100000@ltoi.iap.physik.tu-darmstadt.de \
--to=schmid@ltoi.iap.physik.tu-darmstadt.de \
--cc=egcs@cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).