-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUILD: 1.25.0: make clobber errors #18455
Comments
Thanks for filing this @tonycurtis ! (I'm assuming that this is not holding you up in any way, but please give a shout if I'm incorrect in that). |
On Sep 24, 2021, at 2:29 PM, Brad Chamberlain ***@***.***> wrote:
Thanks for filing this @tonycurtis <https://github.com/tonycurtis> ! (I'm assuming that this is not holding you up in any way, but please give a shout if I'm incorrect in that).
No, just testing…
|
For the team, |
@mppf: I believe that this behavior is because in these lines:
|
Yes, I think a quick fix would be to adjust these to no-op if the command fails. However in fact I would advocate for moving this logic into the Python scripts. |
Improve compiler configuration This PR takes several steps to improve the configuration visible in `printchplenv`. It is intended to resolve the following issues: * #18450 * Cray/chapel-private#2520 * Cray/chapel-private#2529 * #18455 It takes the following steps: * Adjusts make/compiler/Makefile.clang to avoid running the compiler when `CHPL_TARGET_COMPILER=llvm` in order to avoid problems with `make clobber` with `CHPL_LLVM=bundled`. We can avoid running the compiler since we only build with LLVM 11+ and the associated clang defaults to C17 and C++14. In the future, it would be nice to move this logic to the Python scripts, but I did not take that on here. * Removes CPU feature tables since these have not been properly updated in a long time and have limited benefit. This reduces maintenance and the likelihood a user will run into problems when using an architecture not specifically tested. However, removing these feature tables means we can no longer give warnings/errors when the configuration requested appears to be something that could not run. * Uses a simple table to map PrgEnv CPU names to clang/llvm architecture names. This is a stopgap solution until we find a better way. * Changes CC/CXX support (added in PR #17923) to make setting these variables have less of a confusing impact (per discussion in #18450): * they do not prevent `CHPL_TARGET_COMPILER` defaulting to `llvm` when that makes sense * they are unused if other `CHPL_*_COMPILER` / `CHPL_*_CC` / `CHPL_*_CXX` are set * they apply only to the host configuration when working on a system using a PrgEnv compiler Reviewed by @daviditen - thanks! - [x] test on a Cray PrgEnv system - [x] full local testing
I've verified that PR #18485 fixes this issue for me so I'm closing it. We can reopen it / create a new issue if the issue appears in some configuration I haven't tested. |
Thanks, Michael! |
Summary of Problem
Steps to Reproduce
Compile command:
make clobber
Execution command:
N/A
Configuration Information
chpl --version
:$CHPL_HOME/util/printchplenv --anonymize
:gcc --version
orclang --version
:The text was updated successfully, but these errors were encountered: