You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- leaving lots of perf on the table; distros moving to x64-v2 or [even](https://www.phoronix.com/news/CentOS-ISA-Experiment-Perform) v3 baseline ()
53
+
-[CF issue](https://github.com/conda-forge/conda-forge.github.io/issues/1261) open since ~2.5yrs; [CEP issue](https://github.com/conda-incubator/ceps/issues/59) a few months ago -- next steps?
54
+
- (IF,CHL) We could probably re-purpose the existing `__archspec` virtual package to expose/proxy the HWCAPS/feature level; would not require additional changes conda to get some support for tuned packages
55
+
- See https://github.com/conda-incubator/ceps/issues/59#issuecomment-1636844274
- (CHL) CEP potentially goes way deeper and would expose things like individual CPU feature flags. (Original in-person discussion at SciPy 2023 was around discovering specific AVX-512, AES-NI, and ARM instructions.)
58
+
-[X] (BH) Where is the best place to learn about/peek into conda-forge build automation?
59
+
- Feedstock builds: conda-smithy provides the starting configuration, conda-forge-ci-setup handles some stuff at runtime, docker-images creates the base image for Linux. Automation around feedstocks... regro/cf-scripts is the start.
60
+
-https://cf-infra-docs.netlify.app/docs/fundamentals/life-cycle/ for some big picture docs (non-official)
0 commit comments