bazelbuild / bazelbuild/platforms

i386 vs x86_32

Open
#83 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Starlark
Stars
124
Forks
94
PR merge metrics
No merged PRs in 30d

Description

Currently, there are two separate cpu constraint values `x86_32` and `i386`. The intended use is not entirely clear to me.
As I understand it, "x86" is the whole family of instruction set architectures (also known as Intel Architecture "IA-32"), and, _technically_, "i386" (also known as 80386) is the first processor in the line of this family.
However, the two terms are frequently used interchangeably; for example, the Debian port supporting all 32 bit x86 CPUs is called "i386" (see https://www.debian.org/ports/).

Is this `i386` cpu constraint value really intended to refer specifically to (the instruction set of the) original 80386 Intel processor? Or does it rather refer to the entire family, just like `x86_32`?
If it's the former, would it make sense to add a big warning note to indicate that you probably don't want to use this?
If it's the latter, would it make sense to change `i386` to be merely an alias for `x86_32`?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.