vector.com|Contact
Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

apple*
Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Search:
Advanced search

VectorCAST CUDA Example

Last updated: 2019-12-09

To allow for an intuitive workflow, VectorCAST/QA has been extended to automatically build a project that has N separate coverage environments: one for the host, and one for each of the GPUs.  Combining these N environments into a single project allows you to build an instrumented application that can collect coverage for all architectures.  As test cases are run using VectorCAST/QA, the code coverage information is “split” into the N projects, and combined at the project level.  This means that you can easily view code coverage for either the complete file or for the architecture-specific parts independently.

This folder has a CUDA example for VectorCAST.

  1. Download the KB_1476_cuda-demo.zip to the working directory
  2. Untar the demo


     
  3. Open the localization.sh file and edit to fit the current working directories
    • The source files for the demo is currently already included with the release
    • Edit VECTOR_LICENSE_FILE to the license file/server in use
    • Edit VECTORCAST_DIR to the location of VectorCAST installed


       
    • Optional: Edit MYPROJECTNAME, testdirname and CUDABIN if not satisfied with the default


       
    • Save the changes
  4. Run the createdemo.sh file


     
  5. The script will automatically build and execute the CUDA example and open VectorCAST when done
  6. Open the Project via File | Open and then selecting the newly constructed environment


     
  7. Based on the capability of the machine on which VectorCAST is run, the system testing environments will have different coverage results.
     
 
Article Options
2019-12-09
Views: 79
Rate this article: