From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] nds32: toolchains for building ?
Date: Thu, 10 Nov 2011 21:42:56 -0500 [thread overview]
Message-ID: <201111102142.57775.vapier@gentoo.org> (raw)
In-Reply-To: <CACCg+XNPxv1JqrBR_yY6G4Lx=x8dPoc3B9+FhtRywmgqZ6qkxg@mail.gmail.com>
On Thursday 10 November 2011 21:01:37 Macpaul Lin wrote:
> 2011/11/11 Mike Frysinger:
> > so the ISA version only affects the generated libraries right ? i can
> > still use any of the compilers to output any ISA version ?
>
> Unfortunately, wrong.
>
> ISA will affect the assembly and binary patterns, also some basic
> stack operation.
right, which is why gcc ports have options like -march=, -mcpu=, -mtune=,
etc... this way you only need 1 gcc to support all these different ISAs.
nds32le-linux-gcc -march=v0 -c ......
nds32le-linux-gcc -march=v1 -c ......
nds32le-linux-gcc -march=v1f -c ......
what i meant was that you don't have to configure gcc for a specific ISA.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111110/c96126ab/attachment.pgp
next prev parent reply other threads:[~2011-11-11 2:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 17:58 [U-Boot] nds32: toolchains for building ? Mike Frysinger
2011-11-04 8:24 ` 馬克泡
2011-11-04 22:22 ` Mike Frysinger
2011-11-04 23:20 ` Mike Frysinger
2011-11-05 1:35 ` 馬克泡
2011-11-05 17:04 ` Mike Frysinger
2011-11-10 6:22 ` Macpaul Lin
2011-11-10 16:28 ` Mike Frysinger
2011-11-10 17:01 ` Macpaul Lin
2011-11-10 17:12 ` Mike Frysinger
2011-11-11 2:01 ` Macpaul Lin
2011-11-11 2:08 ` Macpaul Lin
2011-11-11 2:42 ` Mike Frysinger [this message]
2011-11-11 2:53 ` Macpaul Lin
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=201111102142.57775.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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