| /llvm-project/llvm/utils/docker/scripts/llvm_checksum/ |
| H A D | project_tree.py | 29 all_projects: projects in the LLVM checkout.
63 When False, relative paths for each projects points to a separate
67 # FIXME: cover all of llvm projects.
69 # Projects that reside inside 'projects/' in a single source tree checkout.
78 # Projects that reside inside 'tools/' in a single source tree checkout.
82 projects = [LLVMProject("llvm", "")]
83 projects += [
84 LLVMProject(p, os.path.join("projects", p)) for p in ORDINARY_PROJECTS
86 projects += [LLVMProject(p, os.path.join("tools", p)) for p in TOOLS_PROJECTS]
87 projects.append(
[all …]
|
| H A D | llvm_checksum.py | 33 help="ignore projects from reference_file "
72 def ComputeLLVMChecksums(root_path, projects): argument
77 projects: a list of LLVMProject instances, which describe checkout paths,
101 for proj in projects:
123 WalkProjectFiles(root_path, projects, proj, add_file_hash)
174 When True, reference_checksums may contain more projects than
175 new_checksums. Projects missing from new_checksums are ignored.
177 for the same set of projects. If there is a project in
|
| /llvm-project/clang/utils/analyzer/ |
| H A D | SATest.py | 10 PROJECTS_DIR = os.path.join(SCRIPTS_DIR, "projects")
40 projects = get_projects(parser, args)
43 projects,
89 for project in project_map.projects:
96 projects = get_projects(parser, args)
97 benchmark = Benchmark(projects, args.iterations, args.output)
111 projects = project_map.projects
113 def filter_projects(projects, predicate, force=False): argument
118 for project in projects
121 if args.projects:
[all …]
|
| H A D | ProjectMap.py | 11 DEFAULT_MAP_FILE = "projects.json"
39 of possible sizes. If the user wants to filter projects by one of the
40 possible sizes, we want projects with UNSPECIFIED size to be filtered out
114 Project map stores info about all the "registered" projects.
145 self._save(self.projects, self.path)
154 self.projects = self._parse(raw_projects)
194 def _save(projects: List[ProjectInfo], path: str):
196 json.dump(ProjectMap._convert_infos_to_dicts(projects), output, indent=2)
199 def _convert_infos_to_dicts(projects: List[ProjectInfo]) -> List[JSON]:
200 return [ProjectMap._convert_info_to_dict(project) for project in projects]
|
| H A D | SATestBenchmark.py | 5 the analyzer on a set projects. Right now, this includes measuring
36 multiple times for the given set of projects and stores results in the
40 def __init__(self, projects: List[ProjectInfo], iterations: int, output_path: str):
41 self.projects = projects
46 results = [self._benchmark_project(project) for project in self.projects]
91 # Leave only rows for projects common to both dataframes.
|
| /llvm-project/llvm/docs/Proposals/ |
| H A D | GitHubMove.rst | 2 Moving LLVM Projects to GitHub
77 In addition, because Git seems to be replacing many OSS projects' version
85 projects. Any of these could replace the code-hosting infrastructure that we
103 The current SVN repository hosts all the LLVM sub-projects alongside each other.
105 all LLVM sub-projects.
168 Git views for the sub-projects (if the monorepo is selected).
212 sub-projects in a single source tree. It is often referred to as a monorepo and
214 own top-level directory. Not all sub-projects are used for building toolchains.
217 Putting all sub-projects in a single checkout makes cross-project refactoring
220 * New sub-projects can be trivially split out for better reuse and/or layering
[all …]
|
| /llvm-project/llvm/utils/release/ |
| H A D | test-release.sh | 276 # Projects list
277 projects="llvm;clang"
279 projects="${projects:+$projects;}clang-tools-extra"
295 projects="${projects:+$projects;}openmp"
298 projects="${projects
[all...] |
| /llvm-project/libcxx/ |
| H A D | appveyor-reqs-install.cmd | |
| H A D | appveyor.yml | |
| /llvm-project/clang/www/ |
| H A D | related.html | 7 <title>Clang Related Projects</title>
14 <h1>Clang Related Projects</h1>
16 <p>As Clang matures, more and more projects are being built atop the Clang
17 libraries and other open source projects are starting their own Clang
20 related projects.</p>
92 …DXR is a code search and navigation tool aimed at making sense of large projects like Firefox. It …
103 …sion framework which uses LLVM/Clang to analyze and visualize C and C++ projects. It also supports…
114 …er toolchain. It provides a user interface to execute analysis of C/C++ projects with Clang SA and…
|
| /llvm-project/llvm/test/tools/llvm-debuginfo-analyzer/DWARF/ |
| H A D | 06-dwarf-full-logical-view.test | 31 ; ONE-NEXT: {Directory} '/data/projects/tests/input/general'
39 ; ONE-NEXT: [0x00000000a0][002] {Source} '/data/projects/tests/input/general/test.cpp'
50 ; ONE-NEXT: [0x000000001c][004] 5 {Line} {NewStatement} '/data/projects/tests/inpu…
52 ; ONE-NEXT: [0x0000000023][004] 6 {Line} {NewStatement} '/data/projects/tests/inpu…
55 ; ONE-NEXT: [0x000000002f][004] 8 {Line} {NewStatement} '/data/projects/tests/inpu…
70 ; ONE-NEXT: [0x0000000000][003] 2 {Line} {NewStatement} '/data/projects/tests/input/…
78 …00012][003] 3 {Line} {NewStatement} {PrologueEnd} '/data/projects/tests/input/gener…
81 ; ONE-NEXT: [0x0000000032][003] 8 {Line} '/data/projects/tests/input/general/test.cp…
83 ; ONE-NEXT: [0x0000000035][003] 9 {Line} {NewStatement} '/data/projects/tests/input/…
87 …0003a][003] 9 {Line} {NewStatement} {EndSequence} '/data/projects/tests/input/gener…
|
| /llvm-project/llvm/tools/ |
| H A D | CMakeLists.txt | 39 # Projects supported via LLVM_EXTERNAL_*_SOURCE_DIR need to be explicitly
51 # file as external projects.
67 # This is explicitly added at the end _after_ all tool projects so that it can
68 # scrape up tools from other projects into itself.
|
| /llvm-project/polly/www/ |
| H A D | projects.html | 16 <h1>Open Projects</h1>
19 LLVM Polly keeps here a list of open projects which each of themselves would
20 be a great contribution to Polly. All of these projects are meant to be self
21 contained and should take a newcomer around 3-4 months of work. The projects
24 Code</a> projects. In case you are interested in a Google Summer of code
|
| /llvm-project/.github/workflows/ |
| H A D | llvm-project-tests.yml | 11 projects:
29 projects:
59 group: llvm-project-${{ github.workflow }}-${{ inputs.projects }}-${{ inputs.python_version }}${{ github.ref }}
136 -DLLVM_ENABLE_PROJECTS="${{ inputs.projects }}" \
148 if: "!startsWith(matrix.os, 'windows') && contains(inputs.projects, 'libclc')"
|
| /llvm-project/libcxx/docs/Status/ |
| H A D | Zip.rst | |
| H A D | PSTL.rst | 17 used to track both the status of the sub-projects of the PSTL and who is
18 assigned to these sub-projects. This is imperative to effective implementation
25 Sub-Projects in the Implementation Effort
|
| H A D | Parallelism.rst | 16 It is used to track both the status of the sub-projects of the effort and who
17 is assigned to these sub-projects. This avoids duplicating effort.
23 Sub-projects in the Implementation Effort
|
| H A D | Format.rst | 17 track both the status of the sub-projects of the Format library and who is assigned to
18 these sub-projects. This is imperative to effective implementation so that work is not
27 Sub-Projects in the Format library
|
| H A D | Spaceship.rst | |
| /llvm-project/llvm/utils/gn/ |
| H A D | TODO.txt | 3 - more projects (lldb, check- targets for compiler-rt's asan/ubsan/msan/tsan)
4 - once there are more projects, have an llvm_enable_projects arg, modeled
6 - a check-all build target that runs test of all projects
|
| /llvm-project/llvm/projects/ |
| H A D | CMakeLists.txt | 1 # Discover the projects that use CMake in the subdirectories.
29 # Add the projects in reverse order of their dependencies so that the
30 # dependent projects can see the target names of their dependencies.
|
| /llvm-project/clang/docs/analyzer/user-docs/ |
| H A D | CommandLineUsage.rst | 4 This document provides guidelines for running the static analyzer from the command line on whole projects.
24 2. CodeChecker_ is a driver and web server that runs the static analyzer on your projects on demand and maintains a database of issues.
134 Most projects can be built in a "debug" mode that enables assertions. Assertions are picked up by the static analyzer to prune infeasible paths, which in some cases can greatly reduce the number of false positives (bogus error reports) emitted by the tool.
157 Analyzing iPhone Projects
160 Conceptually Xcode projects for iPhone applications are nearly the same as their cousins for desktop applications. **scan-build** can analyze these projects as well, but users often encounter problems with just building their iPhone projects from the command line because there are a few extra preparative steps they need to take (e.g., setup code signing).
165 The absolute easiest way to analyze iPhone projects is to use the `Analyze feature in Xcode <https://developer.apple.com/library/ios/recipes/xcode_help-source_editor/chapters/Analyze.html#//apple_ref/doc/uid/TP40009975-CH4-SW1>`_ (which is based on the static analyzer). There a user can analyze their project right from a menu without most of the setup described later.
189 Recall that **scan-build** analyzes your project by using a compiler to compile the project and ``clang`` to analyze your project. The script uses simple heuristics to determine which compiler should be used (it defaults to ``clang`` on Darwin and ``gcc`` on other platforms). When analyzing iPhone projects, **scan-build** may pick the wrong compiler than the one Xcode would use to build your project. For example, this could be because multiple versions of a compiler may be installed on your system, especially if you are developing for the iPhone.
|
| /llvm-project/llvm/test/tools/llvm-debuginfo-analyzer/WebAssembly/Inputs/ |
| H A D | pr-46466-clang.s | 3 .file 1 "/data/projects/scripts/regression-suite/input/general" "pr-46466.cpp"
213 ….asciz "clang version 19.0.0git (/data/projects/llvm-root/llvm-project/clang 2db6703f0c257d293df45…
217 .asciz "/data/projects/scripts/regression-suite/input/general" # string offset=124
232 ….ident "clang version 19.0.0git (/data/projects/llvm-root/llvm-project/clang 2db6703f0c257d293df45…
247 ….ascii "19.0.0git (/data/projects/llvm-root/llvm-project/clang 2db6703f0c257d293df455e2dff8c1fb695…
|
| /llvm-project/ |
| H A D | .gitignore | 70 /clang/utils/analyzer/projects/*/CachedSource
71 /clang/utils/analyzer/projects/*/PatchedSource
72 /clang/utils/analyzer/projects/*/ScanBuildResults
73 /clang/utils/analyzer/projects/*/RefScanBuildResults
|
| /llvm-project/llvm/utils/gn/secondary/third-party/unittest/ |
| H A D | unittest.gni | 29 # 2. The CMake build doesn't put the unit tests of all projects (clang,
31 # be name collisions between test binaries from separate projects.
37 # constraints that test binaries of different projects should go in
|