summaryrefslogtreecommitdiff
path: root/.github/ISSUE_TEMPLATE
diff options
context:
space:
mode:
authorScott Wittenburg <scott.wittenburg@kitware.com>2020-11-12 11:46:15 -0700
committerGitHub <noreply@github.com>2020-11-12 10:46:15 -0800
commitfbbd71d3d747feeae0199f85f3213a3bb4f5fdc7 (patch)
tree5294f79fbb107855229a1cab05a0c5ef9f69ad4a /.github/ISSUE_TEMPLATE
parent2a8dba48dad0d133eb7435df6ab318c3722a8d6e (diff)
downloadspack-fbbd71d3d747feeae0199f85f3213a3bb4f5fdc7.tar.gz
spack-fbbd71d3d747feeae0199f85f3213a3bb4f5fdc7.tar.bz2
spack-fbbd71d3d747feeae0199f85f3213a3bb4f5fdc7.tar.xz
spack-fbbd71d3d747feeae0199f85f3213a3bb4f5fdc7.zip
Pipelines: Compare target family instead of architecture (#19884)
In compiler bootstrapping pipelines, we add an artificial dependency between jobs for packages to be built with a bootstrapped compiler and the job building the compiler. To find the right bootstrapped compiler for each spec, we compared not only the compiler spec to that required by the package spec, but also the architectures of the compiler and package spec. But this prevented us from finding the bootstrapped compiler for a spec in cases where the architecture of the compiler wasn't exactly the same as the spec. For example, a gcc@4.8.5 might have bootstrapped a compiler with haswell as the architecture, while the spec had broadwell. By comparing the families instead of the architecture itself, we know that we can build the zlib for broadwell with the gcc for haswell.
Diffstat (limited to '.github/ISSUE_TEMPLATE')
0 files changed, 0 insertions, 0 deletions