| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 11/08/15 06:11 AM, Leno Hou wrote: |
| 5 |
> I think ppc64le would become popular, |
| 6 |
> https://en.wikipedia.org/wiki/Ppc64. |
| 7 |
> |
| 8 |
> 1. enable porting x86 Linux based application with minimal effort. |
| 9 |
> 2. Some PowerPC user, little endian apparently feels cheap, wrong, |
| 10 |
> and PCish. 3. Other distrbutions like Ubuntu, Redhat and SUSE |
| 11 |
> already support little endian in powerpc. |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
In terms of the codepaths, what's different between ppc64le vs ppc64, |
| 16 |
and ppc64le vs amd64 ? Obviously kernels will differ, but in terms of |
| 17 |
C/C++/other compiled source code what needs to change? |
| 18 |
|
| 19 |
If all this needs is its own profile for a CHOST/CBUILD specification |
| 20 |
and it can leverage an existing keyword, then this should be rather |
| 21 |
simple to implement yes? |
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2 |
| 27 |
|
| 28 |
iF4EAREIAAYFAlXKB7UACgkQAJxUfCtlWe1sbQD+KcbYpfo56GrLIVlFyw2iXbMB |
| 29 |
ZOWzuvyI8SVq/DY0SQMBAJgDIjCza8QyUgWEtq2/g5Yu+uWiCibf2ouMeNAOkQ33 |
| 30 |
=YoUg |
| 31 |
-----END PGP SIGNATURE----- |
Archives