From: Esben Haabendal <esben.haabendal@dev.prevas.dk>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: crossgcc@sourceware.org
Subject: Re: Request for testing: canadian rework
Date: Sat, 21 Apr 2012 18:46:00 -0000 [thread overview]
Message-ID: <87y5pox6t7.fsf@dev.prevas.dk> (raw)
In-Reply-To: <201204162355.07157.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Mon, 16 Apr 2012 23:55:06 +0200")
"Yann E. MORIN" <yann.morin.1998@free.fr> writes:
> Changes (from 4.000 feet high):
> - no need for a pre-exisiting x-compiler for the target
> - a complete x-compiler for target is built for internal use, but is not
> exported for the user to use
Will it still be possible to use a pre-existing x-compiler for target?
When building let's say 3 canadian-cross crompilers, fx.
i686-linux -> arm-linux
x86_64-linux -> arm-linux
mingw32 -> arm-linux
It would be nice to be able to not have to build the same target
x-compiler three times.
> So yes, build time has increased significantly because we build one more
> compiler suite. But this had to be done previously, too, albeit in a
> separate incantation to crosstool-NG, so all-in-all, we should be roughly
> back on-track, time-wise, even a little bit faster (~ 3%-5% faster) from
> my little testing.
For the single canadian case, that is.
> What could yet be improved in this area:
> - change the {cross,cross-native,canadian} selection from a radio-button
> to a multi-select, so it is possible to build all three compilers in one
> ct-ng incantation, thus guaranteeing homgeneity across all three
Nice.
But if you need more than one canadian-cross compiler...
> - these two will first need proper prefix vs. destdir support (which is
> totally lacking now)
> - 'cross-native' will need some love, as it needs to generate a non-
> sysrooted toolchain (or use a sysroot of / which looks odd)
> - possibly drop the 'native' case, for which I don't really see the point
> (there's no code right now, anyway)
>
> Regards,
> Yann E. MORIN.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-04-21 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 21:55 Yann E. MORIN
2012-04-21 18:46 ` Esben Haabendal [this message]
2012-04-23 21:25 ` Yann E. MORIN
2012-04-24 18:58 ` Esben Haabendal
2012-08-06 6:32 ` Esben Haabendal
2012-08-06 17:01 ` Yann E. MORIN
2012-08-06 18:50 ` Esben Haabendal
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=87y5pox6t7.fsf@dev.prevas.dk \
--to=esben.haabendal@dev.prevas.dk \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@free.fr \
/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).