From 19303b8e35e2bbf427e0363a765f09e576fdf9c5 Mon Sep 17 00:00:00 2001 From: guojun Date: Fri, 28 Jul 2023 17:09:44 +0800 Subject: [PATCH 1/3] [Sanitizer] Support HWAddress in ohos targets Issue: https://gitee.com/openharmony/third_party_llvm-project/issues/I7EU84 Signed-off-by: guojun --- clang/lib/Driver/ToolChains/OHOS.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/clang/lib/Driver/ToolChains/OHOS.cpp b/clang/lib/Driver/ToolChains/OHOS.cpp index 551ae2ec821c..916e39d2187d 100644 --- a/clang/lib/Driver/ToolChains/OHOS.cpp +++ b/clang/lib/Driver/ToolChains/OHOS.cpp @@ -415,6 +415,7 @@ SanitizerMask OHOS::getSupportedSanitizers() const { Res |= SanitizerKind::Scudo; Res |= SanitizerKind::KernelAddress; Res |= SanitizerKind::KernelMemory; + Res |= SanitizerKind::HWAddress; // TODO: Support TSAN and HWASAN and update mask. return Res; } -- Gitee From 72017db617f61abe0ab57a2352760120cd72e9c1 Mon Sep 17 00:00:00 2001 From: guojungwx1260019 Date: Fri, 28 Jul 2023 11:58:00 +0000 Subject: [PATCH 2/3] update README.md. Signed-off-by: guojungwx1260019 Signed-off-by: guojungwx1260019 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7a3f4e6fd076..93e9c7138c5a 100644 --- a/README.md +++ b/README.md @@ -107,7 +107,7 @@ This is an example work-flow and configuration to get and build the LLVM source: In most cases, you get the best performance if you specify the number of CPU threads you have. On some Unix systems, you can specify this with ``-j$(nproc)``. - * For more information see [CMake](https://llvm.org/docs/CMake.html). + * For more information see [CMake](https://llvm.org/docs/CMake.html) Consult the [Getting Started with LLVM](https://llvm.org/docs/GettingStarted.html#getting-started-with-llvm) -- Gitee From 8f06fee7505d948047c404d5516d70d637493b6b Mon Sep 17 00:00:00 2001 From: guojungwx1260019 Date: Fri, 28 Jul 2023 12:09:54 +0000 Subject: [PATCH 3/3] =?UTF-8?q?=E5=88=A0=E9=99=A4=E6=96=87=E4=BB=B6=20READ?= =?UTF-8?q?ME.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 125 ------------------------------------------------------ 1 file changed, 125 deletions(-) delete mode 100644 README.md diff --git a/README.md b/README.md deleted file mode 100644 index 93e9c7138c5a..000000000000 --- a/README.md +++ /dev/null @@ -1,125 +0,0 @@ -# The LLVM Compiler Infrastructure - -This directory and its sub-directories contain the source code for LLVM, -a toolkit for the construction of highly optimized compilers, -optimizers, and run-time environments. - -The README briefly describes how to get started with building LLVM. -For more information on how to contribute to the LLVM project, please -take a look at the -[Contributing to LLVM](https://llvm.org/docs/Contributing.html) guide. - -## Getting Started with the LLVM System - -Taken from [here](https://llvm.org/docs/GettingStarted.html). - -### Overview - -Welcome to the LLVM project! - -The LLVM project has multiple components. The core of the project is -itself called "LLVM". This contains all of the tools, libraries, and header -files needed to process intermediate representations and convert them into -object files. Tools include an assembler, disassembler, bitcode analyzer, and -bitcode optimizer. It also contains basic regression tests. - -C-like languages use the [Clang](http://clang.llvm.org/) frontend. This -component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode --- and from there into object files, using LLVM. - -Other components include: -the [libc++ C++ standard library](https://libcxx.llvm.org), -the [LLD linker](https://lld.llvm.org), and more. - -### Getting the Source Code and Building LLVM -We recommend that you base on the guide [llvm-build](https://gitee.com/openharmony-sig/third_party_llvm-project/blob/master/llvm-build/README.md) to get the source code and build it for OpenHarmony platform. - -The LLVM Getting Started documentation may be out of date. The [Clang -Getting Started](http://clang.llvm.org/get_started.html) page might have more -accurate information. - -This is an example work-flow and configuration to get and build the LLVM source: - -1. Checkout LLVM (including related sub-projects like Clang): - - * ``git clone https://github.com/llvm/llvm-project.git`` - - * Or, on windows, ``git clone --config core.autocrlf=false - https://github.com/llvm/llvm-project.git`` - -2. Configure and build LLVM and Clang: - - * ``cd llvm-project`` - - * ``cmake -S llvm -B build -G [options]`` - - Some common build system generators are: - - * ``Ninja`` --- for generating [Ninja](https://ninja-build.org) - build files. Most llvm developers use Ninja. - * ``Unix Makefiles`` --- for generating make-compatible parallel makefiles. - * ``Visual Studio`` --- for generating Visual Studio projects and - solutions. - * ``Xcode`` --- for generating Xcode projects. - - Some common options: - - * ``-DLLVM_ENABLE_PROJECTS='...'`` and ``-DLLVM_ENABLE_RUNTIMES='...'`` --- - semicolon-separated list of the LLVM sub-projects and runtimes you'd like to - additionally build. ``LLVM_ENABLE_PROJECTS`` can include any of: clang, - clang-tools-extra, cross-project-tests, flang, libc, libclc, lld, lldb, - mlir, openmp, polly, or pstl. ``LLVM_ENABLE_RUNTIMES`` can include any of - libcxx, libcxxabi, libunwind, compiler-rt, libc or openmp. Some runtime - projects can be specified either in ``LLVM_ENABLE_PROJECTS`` or in - ``LLVM_ENABLE_RUNTIMES``. - - For example, to build LLVM, Clang, libcxx, and libcxxabi, use - ``-DLLVM_ENABLE_PROJECTS="clang" -DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi"``. - - * ``-DCMAKE_INSTALL_PREFIX=directory`` --- Specify for *directory* the full - path name of where you want the LLVM tools and libraries to be installed - (default ``/usr/local``). Be careful if you install runtime libraries: if - your system uses those provided by LLVM (like libc++ or libc++abi), you - must not overwrite your system's copy of those libraries, since that - could render your system unusable. In general, using something like - ``/usr`` is not advised, but ``/usr/local`` is fine. - - * ``-DCMAKE_BUILD_TYPE=type`` --- Valid options for *type* are Debug, - Release, RelWithDebInfo, and MinSizeRel. Default is Debug. - - * ``-DLLVM_ENABLE_ASSERTIONS=On`` --- Compile with assertion checks enabled - (default is Yes for Debug builds, No for all other build types). - - * ``cmake --build build [-- [options] ]`` or your build system specified above - directly. - - * The default target (i.e. ``ninja`` or ``make``) will build all of LLVM. - - * The ``check-all`` target (i.e. ``ninja check-all``) will run the - regression tests to ensure everything is in working order. - - * CMake will generate targets for each tool and library, and most - LLVM sub-projects generate their own ``check-`` target. - - * Running a serial build will be **slow**. To improve speed, try running a - parallel build. That's done by default in Ninja; for ``make``, use the option - ``-j NNN``, where ``NNN`` is the number of parallel jobs to run. - In most cases, you get the best performance if you specify the number of CPU threads you have. - On some Unix systems, you can specify this with ``-j$(nproc)``. - - * For more information see [CMake](https://llvm.org/docs/CMake.html) - -Consult the -[Getting Started with LLVM](https://llvm.org/docs/GettingStarted.html#getting-started-with-llvm) -page for detailed information on configuring and compiling LLVM. You can visit -[Directory Layout](https://llvm.org/docs/GettingStarted.html#directory-layout) -to learn about the layout of the source code tree. - -## Getting in touch - -Join [LLVM Discourse forums](https://discourse.llvm.org/), [discord chat](https://discord.gg/xS7Z362) or #llvm IRC channel on [OFTC](https://oftc.net/). - -The LLVM project has adopted a [code of conduct](https://llvm.org/docs/CodeOfConduct.html) for -participants to all modes of communication within the project. - -For the llvm construction of openharmony, please refer to [llvm-build](https://gitee.com/openharmony-sig/third_party_llvm-project/blob/master/llvm-build/README.md). -- Gitee