search for: troyj

...I've looked through the options list and read some of the lld code, but so far have not been able to find a solution. Thanks, Troy Johnson, Ph.D. | Manager & Lead, Compiler Optimization Cray, a Hewlett Packard Enterprise company 2131 Lindau Lane, Suite 1000 | Bloomington, MN 55425 troyj at cray.com<mailto:prosien at cray.com> www.cray.com<http://www.cray.com> [signature_957042053]<https://www.cray.com/> [signature_921593785]<https://twitter.com/cray_inc> [signature_1210040077] <https://www.youtube.com/channel/UCS483ZExauoVgpG8dLn5p1w> [signature...

...ere. Maybe I should move everything under test-suite/External and more closely mimic these SPEC CMakeLists.txt? -Troy > -----Original Message----- > From: chris.matthews at apple.com <chris.matthews at apple.com> > Sent: Friday, November 16, 2018 12:26 PM > To: Troy Johnson <troyj at cray.com> > Cc: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] [LNT] How to set an env var before executing a test? > > It does not. The prefers way to customize is to use a cmake define. > > Briefly, LNT is first running cmake, then make to build the tests. Then run...

Does the LNT test-suite provide a way to have an environment variable set when executing a test? I can set it outside of LNT (i.e. have it in my environment when LNT is launched) and that works fine, but there does not appear to be a way to set it as part of a test's configuration. There are some lit.local.cfg files scattered throughout the test-suite repository, but messing with os.environ

Restrict is supported by Clang for C++ via __restrict__, so it seems strange to block using this proposed option for C++. That said, this kind of option can be dangerous and should come with a suitable warning. We’ve had a similar option and in practice it’s been used to hunt for performance gains (i.e., turn it on and see what happens), but just because the code runs faster and produces the

Hi, I'm looking for some feedback on pain points people have with FileCheck in terms of missing features to help people interested in working on FileCheck to prioritize the work accordingly. I am personally interested in improving FileCheck on 2 issues whenever time permits it: * being able to test for consecutive lines in arbitrary order, i.e. something akin to CHECK-DAG blocks where