Comments (2)
I'm not inclined to go down this path. It is never ending. Perhaps the X86 space is mostly stable, but the ARM space is growing all the time. Many people take the ARM core and add other pieces they need on the die. They should be able to innovate without having everything enumerated in platforms.
In general, micro level distinguishers should be provided by the compiler toolchains.
from platforms.
Over in Python land, there's 4 different prebuilt interpreters available that vary by micro arch: a generic one, and then 3 that target some different micro archs. These docs talk about them: https://gregoryszorc.com/docs/python-build-standalone/main/running.html#obtaining-distributions:~:text=Intel/AMD%20CPUs.-,x86_64_v2,-%2D*
So, perhaps you'd reconsider having those micro archs here in the platforms repo? If not, perhaps another lighter weight place?
In general, micro level distinguishers should be provided by the compiler toolchains.
That seems rather expensive in this case, though. The binaries are prebuilt, so a compiler toolchain isn't necessarily required. It would also mean the compiler repos would have to be downloaded even if they weren't used -- during toolchain resolution, the constraint has to be evaluated, which then would download that compiler repo, only to have it not match.
from platforms.
Related Issues (20)
- [discussion] Decide whether or not to express FPU nuances for `@platforms//cpu:armv*-m*` constraints HOT 4
- Add presubmit tests to validate platform definitions HOT 1
- Add cpp examples HOT 1
- Migrate `config_settings` from core Bazel to platforms HOT 4
- Platform Commonalities: e.g. Apple, POSIX, etc. HOT 20
- Constraints for ABI HOT 22
- Define a value for "no OS"? HOT 3
- platforms 0.0.6 not published to central registry HOT 1
- How to reference the platform repository. HOT 2
- MacOS being detected as multiple OSes HOT 13
- Repository `@rules_license` is not defined HOT 4
- Prefer cpu:aarch64 to cpu:arm64
- Implement Standard Platform Transitions HOT 2
- Issue specifying linux platform constraint to bazel workspace HOT 3
- platform_data syntax error
- i386 vs x86_32 HOT 1
- When will the next version be released to the Bazel Central Register? HOT 1
- [question] bazel platforms for c/c++ how to distinguish the toolchain while they are same cpu and os
- `//cpu:ppc64` HOT 1
- Support for UEFI targets
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from platforms.