search for: llvm_multisourc

...ct a lot of changes before actually landing it, this is simply to continue the discussion using a concrete example.) http://reviews.llvm.org/D17726 A few questions/todos to start the discussion: 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). 2. There is a single .cpp file testing all operations provided by individual bitcode files. I expect this to change. Instead of using llvm_multisource to have the same test run with specific arguments, each run...

...ode files* from Phabricator. Can you push this on github (or somewhere else)? (or if I missed how to proceed...). Thanks, Mehdi > > A few questions/todos to start the discussion: > 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). > 2. There is a single .cpp file testing all operations provided by individual bitcode files. I expect this to change. Instead of using llvm_multisource to have the same test run with specific arguments, ea...

...to figure how get them "one by one", it would still be more convenient to have an archive or a repo to clone somewhere. >> A few questions/todos to start the discussion: >> 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). A good location would be their own external repository IMO :) >> 2. There is a single .cpp file testing all operations provided by individual bitcode files. I expect this to change. Instead of using ll...

On 18/02/2016 19:12, Alina Sbirlea via llvm-dev wrote: > > > I have more questions for Alina. What kind of tests do you have: > > - "the compiler takes the bitcode and generates code without crashing" > - "the compiled test runs without crashing" > - "the compiled test will produce an output that be checked > against a

...get them "one by one", it would still be more convenient to have an archive or a repo to clone somewhere. > >>> A few questions/todos to start the discussion: >>> 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). > > A good location would be their own external repository IMO :) > >>> 2. There is a single .cpp file testing all operations provided by individual bitcode files. I expect this to change....

...ure how get them "one by one", it would still be more > convenient to have an archive or a repo to clone somewhere. > > A few questions/todos to start the discussion: > 1. What is a good location for these tests? They are in a separate Bitcode > directory atm, but using the llvm_multisource. This may change to more > closely model the approach for external tests (see next item). > > > A good location would be their own external repository IMO :) > > 2. There is a single .cpp file testing all operations provided by > individual bitcode files. I expect this to chan...

...ot;one by one", it would still be more >> convenient to have an archive or a repo to clone somewhere. >> >> A few questions/todos to start the discussion: >> 1. What is a good location for these tests? They are in a separate >> Bitcode directory atm, but using the llvm_multisource. This may change to >> more closely model the approach for external tests (see next item). >> >> >> A good location would be their own external repository IMO :) >> >> 2. There is a single .cpp file testing all operations provided by >> individual bitcode...

...would still be more convenient to have an archive or a repo to clone somewhere. >>>> >>>>>> A few questions/todos to start the discussion: >>>>>> 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). >>>> >>>> A good location would be their own external repository IMO :) >>>> >>>>>> 2. There is a single .cpp file testing all operations provided by ind...

...> > > > > > > > > > > > > > > > > > > > > > > > 1. What is a good location for these tests? They are in a > > > > > > > separate > > > > > > > Bitcode directory atm, but using the llvm_multisource. > > > > > > > This > > > > > > > may > > > > > > > change to more closely model the approach for external > > > > > > > tests > > > > > > > (see > > > > > > > next item)....

...le to figure how get them "one by one", it would still be more convenient to have an archive or a repo to clone somewhere. > > A few questions/todos to start the discussion: > 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). > > A good location would be their own external repository IMO :) > > 2. There is a single .cpp file testing all operations provided by individual bitcode files. I expect this to change. Instead...

...it would still be more >>> convenient to have an archive or a repo to clone somewhere. >>> >>> A few questions/todos to start the discussion: >>> 1. What is a good location for these tests? They are in a separate >>> Bitcode directory atm, but using the llvm_multisource. This may change to >>> more closely model the approach for external tests (see next item). >>> >>> >>> A good location would be their own external repository IMO :) >>> >>> 2. There is a single .cpp file testing all operations provided by >...

...how get them "one by one", it would still be more convenient to have an archive or a repo to clone somewhere. >> >> A few questions/todos to start the discussion: >> 1. What is a good location for these tests? They are in a separate Bitcode directory atm, but using the llvm_multisource. This may change to more closely model the approach for external tests (see next item). >> >> A good location would be their own external repository IMO :) >> >> 2. There is a single .cpp file testing all operations provided by individual bitcode files. I expect this to...

On Thu, Feb 18, 2016 at 10:03 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Feb 18, 2016, at 8:42 AM, Philip Reames via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > On 02/18/2016 06:54 AM, Hal Finkel via llvm-dev wrote: > >> Hi Chandler, et al., > >> > >> While this proposal to put IR into the test suite