From: "sébastien bertoletto" <sbertoletto@gmail.com>
To: gentoo-mips@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>, basile@opensource.dyc.edu
Subject: Re: [gentoo-mips] Re: On MIPS using the same CHOST for all multilib ABIs
Date: Mon, 30 Dec 2013 09:17:07 +0100 [thread overview]
Message-ID: <CAM_cF+=BAMJG3XiYC6VurZ3bBVGdjBm1MCuogd4JTG+OyLfQzw@mail.gmail.com> (raw)
In-Reply-To: <201312300251.54904.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Hello,
Please delete me from the list : *lists.gentoo.org
<http://lists.gentoo.org>*
Thanks,
2013/12/30 Mike Frysinger <vapier@gentoo.org>
> On Sunday 29 December 2013 18:56:14 Mike Frysinger wrote:
> > so to turn your base argument around, we shouldn't be limiting Gentoo to
> > only support CHOSTs that also select ABIs uniquely.
>
> also worth noting: we've been severely limiting ourselves as to the full
> range
> of possibilities. when we say "ABI", we've largely been focusing on the
> most
> common aspect. in reality, an ABI is defined by many more features like:
> - endian (little/big)
> - floating point (hard/soft/etc...)
> - ISA selection (mips1/mips2/mips3/mips4/... or i386/i486/i586/i686/... or
> sse1/sse2/mmx/3dnow!/...)
> there are other aspects too, but these are the obvious ones that people are
> selecting every day. people have one toolchain which can generate code for
> all of these things merely by flag selection, not different CHOST values.
> in
> Gentoo we don't commonly support this as most people don't care, but it has
> been done before.
> -mike
>
--
Sébastien Bertoletto
[-- Attachment #2: Type: text/html, Size: 1961 bytes --]
next prev parent reply other threads:[~2013-12-30 8:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 22:58 [gentoo-mips] On MIPS using the same CHOST for all multilib ABIs Michał Górny
2013-12-28 23:55 ` Markos Chandras
2013-12-29 2:12 ` Mike Frysinger
[not found] ` <20131229163354.35b65df5@gentoo.org>
2013-12-29 18:21 ` Mike Frysinger
2013-12-30 9:44 ` Michał Górny
2013-12-29 21:40 ` [gentoo-mips] " Joshua Kinard
2013-12-29 21:48 ` Markos Chandras
2013-12-29 21:48 ` Michał Górny
2013-12-29 21:48 ` Markos Chandras
2013-12-29 21:52 ` Anthony G. Basile
2013-12-29 22:04 ` Michał Górny
2013-12-29 23:56 ` Mike Frysinger
2013-12-30 7:51 ` Mike Frysinger
2013-12-30 8:17 ` sébastien bertoletto [this message]
2013-12-29 22:13 ` Markos Chandras
2013-12-29 22:19 ` Anthony G. Basile
2013-12-29 22:33 ` Markos Chandras
2013-12-29 23:47 ` Anthony G. Basile
2014-01-16 20:01 ` [gentoo-mips] " Michał Górny
2014-01-16 21:05 ` Anthony G. Basile
2014-01-16 21:24 ` Michał Górny
2014-01-16 22:29 ` Anthony G. Basile
2014-01-17 4:47 ` Michał Górny
2014-01-17 18:20 ` Markos Chandras
2014-01-17 18:36 ` Matt Turner
2014-01-17 19:38 ` Markos Chandras
2014-01-17 21:57 ` Matt Turner
2014-01-17 18:51 ` Michał Górny
2014-01-17 19:44 ` Markos Chandras
2014-01-21 20:52 ` Markos Chandras
2014-01-22 14:24 ` Anthony G. Basile
2014-01-22 14:38 ` Michał Górny
2014-01-22 20:39 ` Markos Chandras
2014-01-22 21:07 ` Anthony G. Basile
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='CAM_cF+=BAMJG3XiYC6VurZ3bBVGdjBm1MCuogd4JTG+OyLfQzw@mail.gmail.com' \
--to=sbertoletto@gmail.com \
--cc=basile@opensource.dyc.edu \
--cc=gentoo-mips@lists.gentoo.org \
--cc=mgorny@gentoo.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