From: Diego Saravia <dsa@unsa.edu.ar>
To: crossgcc@sourceware.org
Subject: conceptual help
Date: Mon, 08 Feb 2010 20:32:00 -0000 [thread overview]
Message-ID: <5b39479c1002081232s16bc722clec4ee1cc4e8b6d87@mail.gmail.com> (raw)
I dont understand why to use i586 i686 x86_64, etc as targets if gcc
produces only one excecutable for all i386 and x86_64 processors
it is not better to have only one gcc-binary, aka i386-gcc for all
that processors and use "i386-gcc -march=i586", "i386-gcc
-march=i686" and "i386-gcc -march=x86_64"?
I was reading http://wiki.osdev.org/GCC_Cross-Compiler and I cant find
any reason to have diferent gcc binaries and binutils for each
processor, only one for each -b gcc backends
thank you for your attention.
--
Diego Saravia
Diego.Saravia@gmail.com
NO FUNCIONA->dsa@unsa.edu.ar
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2010-02-08 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 20:32 Diego Saravia [this message]
2010-02-09 0:53 ` Martin Guy
2010-02-09 2:59 ` Diego Saravia
2010-02-09 8:15 ` Thomas Petazzoni
2010-02-09 17:53 ` Yann E. MORIN
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=5b39479c1002081232s16bc722clec4ee1cc4e8b6d87@mail.gmail.com \
--to=dsa@unsa.edu.ar \
--cc=crossgcc@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).