Hi,
libboost_system-vc141-mt-gd-x32-1_66.lib
Why is this named x32? AFAIK the normal name is x86. -- Olaf
On 28/11/17 09:19, Olaf van der Spek via Boost wrote:
Hi,
libboost_system-vc141-mt-gd-x32-1_66.lib
Why is this named x32? AFAIK the normal name is x86.
Also, x32 also is used to mean something quite different: https://en.wikipedia.org/wiki/X32_ABI (x64 ABI with 4-byte addressing, but all the other extensions available such as extra registers, SSE). Regards, Roger
On Tue, Nov 28, 2017 at 4:28 AM, Roger Leigh via Boost < boost@lists.boost.org> wrote:
On 28/11/17 09:19, Olaf van der Spek via Boost wrote:
Hi,
libboost_system-vc141-mt-gd-x32-1_66.lib
Why is this named x32? AFAIK the normal name is x86.
Also, x32 also is used to mean something quite different: https://en.wikipedia.org/wiki/X32_ABI (x64 ABI with 4-byte addressing, but all the other extensions available such as extra registers, SSE).
This pull request references x32 in Boost.Build: https://github.com/boostorg/build/pull/209 Suggest you open a github issue on Boost.Build. (I would also expect to see "x86", "x86_64", etc...) - Jim
On 28.11.2017 08:07, James E. King, III via Boost wrote:
On Tue, Nov 28, 2017 at 4:28 AM, Roger Leigh via Boost < boost@lists.boost.org> wrote:
On 28/11/17 09:19, Olaf van der Spek via Boost wrote:
Hi,
libboost_system-vc141-mt-gd-x32-1_66.lib Why is this named x32? AFAIK the normal name is x86.
Also, x32 also is used to mean something quite different: https://en.wikipedia.org/wiki/X32_ABI (x64 ABI with 4-byte addressing, but all the other extensions available such as extra registers, SSE).
This pull request references x32 in Boost.Build:
https://github.com/boostorg/build/pull/209
Suggest you open a github issue on Boost.Build.
(I would also expect to see "x86", "x86_64", etc...)
Indeed. I objected to this naming in my review of the above PR, but was ignored. Why does Boost always choose to reinvent wheels and ignore existing practices ?? This seems a severe form of NIH. Stefan -- ...ich hab' noch einen Koffer in Berlin...
Olaf van der Spek wrote:
libboost_system-vc141-mt-gd-x32-1_66.lib
Why is this named x32? AFAIK the normal name is x86.
The suffix is determined by the first letter of the `architecture` Boost.Build property (x86, arm, mips, sparc) concatenated with the `address-model` property (32, 64). Could have gone with the full arch, like x86_32 and x86_64 (and arm_32 and arm_64), but we already have a problem with paths on Windows, no need to make it worse. And people would have complained anyway because it should be "aarch64" instead and so on.
participants (5)
-
James E. King, III -
Olaf van der Spek -
Peter Dimov -
Roger Leigh -
Stefan Seefeld