日 C ur v e1 升级 bazel 到 4.2.2 2 支持 Debian9 、 Debian10 、 Debian11 3 支持 gcc clang 更新内容 Curve1 编译 Debian11-Dockerfile .bazelrc bazel 版本： 4.2.2 （ bazelisk) docker run -v $(pwd):/curve –config=gcc7-later … # use '-faligned-new' to enable C++17 over-aligned new support # 使用 clang 编译 CC=clang CXX=clang++ bazel build …2 制作镜像 docker run -v $(pwd):/curve -v /root/.cache/bazel:/root/.cache/bazel yi01-debian113 修改 & 单元测试 curvefs/test/tools/curvefs_version_tool_test.cpp # 使用 clang 编译 CC=clang CXX=clang++ bazel build curvefs/...THANK YOU

Formatting ☑️� IntelliSense ⌛; ☑️�MSVC ☑️�MSVC Code Analysis ☑️�MSBuild ; CMake ⌛ ; GCC ⌛ ; Clang/LLVM ⌛ ☑️�Stepping ☑️�Parallel Stacks ☑️�Debugger visualizers (.natvis) ☑️�Just My Code debugging Studio integration • MSBuild & CMake support for Windows & Linux • Debugger integration for MSVC and Clang/LLVM Visit https://aka.ms/asan to learn more Announcing today Experimental libFuzzer Support • An Analysis in Visual Studio 🗿 Static Analysis • Code Linters https://aka.ms/cpp/linter • Clang-tidy https://aka.ms/cpp/clangtidy • MSVC Code Analysis https://aka.ms/cpp/ca/bg ⚡ Dynamic Analysis

Requests: Used for all development • Continuous Integration: Azure Pipelines • Code format validation: clang-format, line length, etc. • Projects: Code reviews, C++20 features, etc. • Wiki: Changelog, checklists Sets • Currently up to 12 VMs, each with 16 cores • VMs install VS (with Clang, CMake, Ninja), Python, CUDA • We enforce clang-format for product/test code • Saves an incredible amount of time • Our Our parallelize tool runs it quickly, only on C++ files • Failed checks display the edits that clang-format wants • Building all architectures is very fast • Testing x86/x64 takes about an hour • Many

long* size); Non-C/C++ language. Caller of get_size(). C/C++ binary. Provides get_size(). gcc and clang, sizeof(long) == sizeof(size_t) MSVC, sizeof(long) == 4 Cygwin compile of gcc, sizeof(long) == sizeof(size_t) prepared for a C++ exception – of any sort. The typical result is ... undefined. What compiler flags (clang) were used by the library? By the library consumer? -fsjlj-exceptions? -fignore-exceptions? -fdwarf-exceptions

成机器码， 调用系统提供的 printf 函数，并在终端显示出 Hello, world 。 厂商 C C++ Fortran GNU gcc g++ gfortran LLVM clang clang++ flang 多文件编译与链接 • 单文件编译虽然方便，但也有如下缺点： 1. 所有的代码都堆在一起，不利于模块化和理解。 2. 工程变大时，编译时间变得很长，改动一个地方就得全部重新编译。

Before C++23, assumptions are compiler dependent  Examples:  MSVC and ICC: __assume(expr)  Clang: __builtin_assume(expr)  GCC: Emulated with: if (expr) {} else { __builtin_unreachable(); = 1 // \ + 42 ; std::cout << i; }  It’s undefined by the standard pre C++23! GCC and Clang write 1, MSVC writes 43  C++23 mandates that whitespace after a \ line continuation character

OMPILER_ID.html#variable:CMAKE_%3CLANG%3E_COMPILER_ID 也可以用生成器表达式判断编译器 https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER_ID.html#variable:CMAKE_%3CLANG%3E_COMPILER_ID 生成器表达式也可以做复杂的逻辑判断