Up to [cvs.NetBSD.org] / pkgsrc / lang / clang
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
clang: restore some lost conditional PLIST entries
llvm: updated to 18.1.8 https://releases.llvm.org
clang: updated to 17.0.6 17.0.6 https://releases.llvm.org/17.0.1/tools/clang/docs/ReleaseNotes.html
llvm: updated to 16.0.6 https://releases.llvm.org/16.0.0/docs/ReleaseNotes.html https://releases.llvm.org/16.0.0/tools/clang/docs/ReleaseNotes.html https://releases.llvm.org/16.0.0/tools/clang/tools/extra/docs/ReleaseNotes.html https://releases.llvm.org/16.0.0/tools/lld/docs/ReleaseNotes.html https://releases.llvm.org/16.0.0/projects/libcxx/docs/ReleaseNotes.html
llvm: updated to 15.0.4 LLVM 15.0.4 Changes to the LLVM IR LLVM now uses opaque pointers. This means that different pointer types like i8*, i32* or void()** are now represented as a single ptr type. See the linked document for migration instructions. Renamed llvm.experimental.vector.extract intrinsic to llvm.vector.extract. Renamed llvm.experimental.vector.insert intrinsic to llvm.vector.insert. The constant expression variants of the following instructions have been removed: extractvalue insertvalue udiv sdiv urem srem fadd fsub fmul fdiv frem Added the support for fmax and fmin in atomicrmw instruction. The comparison is expected to match the behavior of llvm.maxnum.* and llvm.minnum.* respectively. callbr instructions no longer use blockaddress arguments for labels. Instead, label constraints starting with ! refer directly to entries in the callbr indirect destination list. Changes to building LLVM Omitting CMAKE_BUILD_TYPE when using a single configuration generator is now an error. You now have to pass -DCMAKE_BUILD_TYPE=<type> in order to configure LLVM. This is done to help new users of LLVM select the correct type: since building LLVM in Debug mode is very resource intensive, we want to make sure that new users make the choice that lines up with their usage. We have also improved documentation around this setting that should help new users. You can find this documentation here. Changes to Loop Optimizations Loop interchange legality and cost model improvements Changes to the AMDGPU Backend 8 and 16-bit atomic loads and stores are now supported Changes to the ARM Backend Added support for the Armv9-A, Armv9.1-A and Armv9.2-A architectures. Added support for the Armv8.1-M PACBTI-M extension. Added support for the Armv9-A, Armv9.1-A and Armv9.2-A architectures. Added support for the Armv8.1-M PACBTI-M extension. Removed the deprecation of ARMv8-A T32 Complex IT blocks. No deprecation warnings will be generated and -mrestrict-it is now always off by default. Previously it was on by default for Armv8 and off for all other architecture versions. Added a pass to workaround Cortex-A57 Erratum 1742098 and Cortex-A72 Erratum 1655431. This is enabled by default when targeting either CPU. Implemented generation of Windows SEH unwind information. Switched the MinGW target to use SEH instead of DWARF for unwind information. Added support for the Cortex-M85 CPU. Added support for a new -mframe-chain=(none|aapcs|aapcs+leaf) command-line option, which controls the generation of AAPCS-compliant Frame Records. Changes to the DirectX Backend DirectX has been added as an experimental target. Specify -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=DirectX in your CMake configuration to enable it. The target is not packaged in pre-built binaries. The DirectX backend supports the dxil architecture which is based on LLVM 3.6 IR encoded as bitcode and is the format used for DirectX GPU Shader programs. Changes to the PowerPC Backend Common PowerPC improvements: * Add a new post instruction selection pass to generate CTR loops. * Add SSE4 and BMI compatible intrinsics implementation. * Supported 16-byte lock free atomics on PowerPC8 and up. * Supported atomic load/store for pointer types. * Supported stack size larger than 2G * Add __builtin_min/__builtin_max/__abs builtins. * Code generation improvements for splat load/vector shuffle/mulli, etc. * Emit VSX instructions for vector loads and stores regardless of alignment. * The mcpu=future has its own ISA now (FutureISA). * Added the ppc-set-dscr option to set the Data Stream Control Register (DSCR). * Bug fixes. AIX improvements: * Supported 64 bit XCOFF for integrated-as path. * Supported X86-compatible vector intrinsics. * Program code csect default alignment now is 32-byte. * Supported auxiliary header in integrated-as path. * Improved alias symbol handling. Changes to the RISC-V Backend A RISCVRedundantCopyElimination pass was added to remove unnecessary zero copies. A RISC-V specific CodeGenPrepare pass was added. The machine outliner was enabled by default for RISC-V at -Oz. Additionally, the newly introduced RISCVMakeCompressible pass will make modify instructions prior to emission at -Oz in order to increase opportunities for the compression with the RISC-V C extension. Various bug fixes and improvements to code generation for the RISC-V vector extensions. Various improvements were made to RISC-V specific optimisation passes such as RISCVSExtWRemoval and RISCVMergeBaseOffset. llc now computes the target ABI based on the target architecture using the same logic as Clang if not explicit ABI is given. generic is now recognized as a valid CPU name and is mapped to generic-rv32 or generic-rv64 depending on the target triple. Support for the experimental Zvfh extension was added, enabling half-precision floating point in vectors. Support for the Zihintpause (Pause Hint) extension. Assembler and disassembler support for the Zfinx and Zdinx (float / double in integer register) extensions. Assembler and disassembler support for the Zicbom, Zicboz, and Zicbop cache management operation extensions. Support for the Zmmul extension (a subextension of the M extension, adding multiplication instructions only). Assembler and disassembler support for the hypervisor extension and for the Sinval supervisor memory-management extension. Changes to the X86 Backend Support half type on SSE2 and above targets following X86 psABI. Support rdpru instruction on Zen2 and above targets. During this release, half type has an ABI breaking change to provide the support for the ABI of _Float16 type on SSE2 and above following X86 psABI. (D107082) The change may affect the current use of half includes (but is not limited to): Frontends generating half type in function passing and/or returning arguments. Downstream runtimes providing any half conversion builtins assuming the old ABI. Projects built with LLVM 15.0 but using early versions of compiler-rt. When you find failures with half type, check the calling conversion of the code and switch it to the new ABI. Changes to the LLVM tools (Experimental) llvm-symbolizer now has --filter-markup to filter Symbolizer Markup into human-readable form. llvm-objcopy has removed support for the legacy zlib-gnu format. llvm-objcopy now allows --set-section-flags src=... --rename-section src=tst. --add-section=.foo1=... --rename-section=.foo1=.foo2 now adds .foo1 instead of .foo2. New features supported on AIX for llvm-ar: AIX big-format archive write operation (D123949) A new object mode option, -X , to specify the type of object file llvm-ar should operate upon (D127864) Read global symbols of AIX big archive (D124865) New options supported for llvm-nm: -X, to specify the type of object file that llvm-nm should examine (D118193) --export-symbols, to create a list of symbols to export (D112735) The LLVM gold plugin now ignores bitcode from the .llvmbc section of ELF files when doing LTO. https://github.com/llvm/llvm-project/issues/47216 llvm-objcopy now supports 32 bit XCOFF. llvm-objdump: improved assembly printing for XCOFF. llc now parses code-model attribute from input file. Changes to LLDB The “memory region” command now has a “–all” option to list all memory regions (including unmapped ranges). This is the equivalent of using address 0 then repeating the command until all regions have been listed. Added “–show-tags” option to the “memory find” command. This is off by default. When enabled, if the target value is found in tagged memory, the tags for that memory will be shown inline with the memory contents. Various memory related parts of LLDB have been updated to handle non-address bits (such as AArch64 pointer signatures): “memory read”, “memory write” and “memory find” can now be used with addresses with non-address bits. All the read and write memory methods on SBProccess and SBTarget can be used with addreses with non-address bits. When printing a pointer expression, LLDB can now dereference the result even if it has non-address bits. The memory cache now ignores non-address bits when looking up memory locations. This prevents us reading locations multiple times, or not writing out new values if the addresses have different non-address bits. LLDB now supports reading memory tags from AArch64 Linux core files. LLDB now supports the gnu debuglink section for reading debug information from a separate file on Windows LLDB now allows selecting the C++ ABI to use on Windows (between Itanium, used for MingW, and MSVC) via the plugin.object-file.pe-coff.abi setting. In Windows builds of LLDB, this defaults to the style used for LLVM’s default target. Other Changes The code for the LLVM Visual Studio integration has been removed. This had been obsolete and abandoned since Visual Studio started including an integration by default in 2019. Added the unwinder, personality, and helper functions for exception handling on AIX. (D100132) (D100504) PGO on AIX: A new implementation that requires linker support (__start_SECTION/__stop_SECTION symbols) available on AIX 7.2 TL5 SP4 and AIX 7.3 TL0 SP2.
clang: fix more PLIST errors under non-default PKG_OPTIONs
clang: fix PLIST error when llvm does not have llvm-target-riscv enabled
lang/clang: llvm update
clang: PLIST fix for Darwin
llvm: update llvm and friends to 13.0.0 Tested on NetBSD-current and 9.1/amd64. Also update packages tightly coupled to llvm, if new versions are available. Mark creduce, include-what-you-use, and zig broken (waiting for a new release). Changes: Non-comprehensive list of changes in this release Windows Control-flow Enforcement Technology: the -ehcontguard option now emits valid unwind entrypoints which are validated when the context is being set during exception handling. Flang is now included in the binary packages released by LLVM. The debuginfo-test project has been renamed cross-project-tests and is now intended for testing components from multiple projects, not just debug information. The new “cross-project-tests” name replaces “debuginfo-test” in LLVM_ENABLE_PROJECTS, and a new check-cross-project-tests target has been added for running all tests in the project. The pre-existing check-debuginfo- test target remains for running just the debug information tests. (D95339 and D96513) Changes to the LLVM IR The inalloca attribute now has a mandatory type field, similar to byval and sret. The opaque pointer type ptr has been introduced. It is still in the process of being worked on and should not be used yet. Using the legacy pass manager for the optimization pipeline is deprecated and will be removed after LLVM 14. In the meantime, only minimal effort will be made to maintain the legacy pass manager for the optimization pipeline. Changes to building LLVM The build system now supports building multiple distributions, so that you can e.g. have one distribution containing just tools and another for libraries (to enable development). See Multi-distribution configurations for details. Changes to the AArch64 Backend Introduced assembly support for Armv9-A’s Realm Management Extension (RME) and Scalable Matrix Extension (SME). Produce proper cross-section relative relocations on COFF Fixed the calling convention on Windows for variadic functions involving floats in the fixed arguments Changes to the ARM Backend Produce proper cross-section relative relocations on COFF Changes to the Hexagon Target The Hexagon target now supports V68/HVX ISA. Changes to the C API The C API functions LLVMGetAlignment and LLVMSetAlignment now allow changing alignment on atomicrmw and cmpxchg instructions A new entry LLVMDIArgListMetadataKind was added to the LLVMMetadataKind enum, representing DIArgLists (D88175) Type attributes have been added to LLVM-C, introducing LLVMCreateTypeAttribute, LLVMGetTypeAttributeValue and LLVMIsTypeAttribute. (D977763’) The LTO_API_VERSION was bumped to 28, introducing a new function lto_set_debug_options for parsing LTO debug options (D92611) LLVMJITTargetSymbolFlags was renamed to LLVMJITSymbolTargetFlags (rG8d718a0bff73af066675a6258c01307937c33cf9) The C API received support for creating custom ORCv2 MaterializationUnits and APIs to retrieve an LLJIT instance’s linking layers. An ABI breaking change for LLVMOrcAbsoluteSymbols was introduced to make it consistent with LLVMOrcCreateCustomMaterializationUnit. (rGc8fc5e3ba942057d6c4cdcd1faeae69a28e7b671) The C API received support for adding ORCv2 object buffers directly to an object layer. (rG7b73cd684a8d5fb44d34064200f10e2723085c33) A breaking change to LLVMGetInlineAsm was introduced, adding a ninth argument LLVMBool CanThrow (D95745) The C API received support for calling into the new pass manager. (D102136) The C API function LLVMIntrinsicCopyOverloadedName has been deprecated. Please migrate to LLVMIntrinsicCopyOverloadedName2 which takes an extra module argument and which also handles unnamed types. (D99173) The C API received support for dumping objects from ORCv2 (rGcec8e69f01c3374cb38c6683058381b96fab8f89) A breaking change to LLVMOrcObjectTransformLayerTransformFunction was introduced, changing the order of the function pointer’s arguments. (rG8962c68ad007a525f9daa987c99eda57e0d0069a) The C API received support for accessing utilities from the LLJIT IRTransformLayer and ThreadSafeModule classes. (D103855) The C API received support for creating lazy-export MaterializationUnits (D104672) The C API function LLVMPassBuilderOptionsSetCoroutines was removed because couroutine passes have been enabled by default. (D105877) comdat noduplicates was renamed to comdat nodeduplicate and as a result, LLVMNoDuplicatesComdatSelectionKind was renamed to LLVMNoDeduplicateComdatSelectionKind. (D106319) Changes to the FastISel infrastructure FastISel no longer tracks killed registers, and instead leaves this to the register allocator. This means that hasTrivialKill() is removed, as well as the OpNIsKill parameters to the fastEmit_*() family of functions. Changes to the LLVM tools The options --build-id-link-{dir,input,output} have been deleted. (D96310) Support for in-order processors has been added to llvm-mca. (D94928) llvm-objdump supports -M {att,intel} now. --x86-asm-syntax is a deprecated internal option which will be removed in LLVM 14.0.0. (D101695) The llvm-readobj short aliases -s (previously --sections) and -t (previously --syms) have been changed to --syms and --section-details respectively, to match llvm-readelf. (D105055) The llvm-nm short aliases -M (--print-armap), -U (--defined-only), and -W (--no-weak) are now deprecated. Use the long form versions instead. The alias --just-symbol-name is now deprecated in favor of --format=just-symbols and -j. (D105330) In lli the default JIT engine switched from MCJIT (-jit-kind=mcjit) to ORC (-jit-kind=orc). (D98931) llvm-rc got support for invoking Clang to preprocess its input. (D100755) llvm-rc got a GNU windres compatible frontend, llvm-windres. (D100756) llvm-ml has improved compatibility with MS ml.exe, managing to assemble more asm files. Changes to LLDB LLDB executable is now included in pre-built LLVM binaries. LLDB now includes full featured support for AArch64 SVE register access. LLDB now supports AArch64 Pointer Authentication, allowing stack unwind with signed return address. LLDB now supports debugging programs on AArch64 Linux that use memory tagging (MTE). Added memory tag read and memory tag write commands. The memory region command will note when a region has memory tagging enabled. Synchronous and asynchronous tag faults are recognised. Synchronous tag faults have memory tag annotations in addition to the usual fault address.
clang: updated to 12.0.1 12.0.1: Non-comprehensive list of changes in this release The builtin intrinsics __builtin_bitreverse8, __builtin_bitreverse16, __builtin_bitreverse32 and __builtin_bitreverse64 may now be used within constant expressions. The builtin intrinsics __builtin_rotateleft8, __builtin_rotateleft16, __builtin_rotateleft32 and __builtin_rotateleft64 may now be used within constant expressions. The builtin intrinsics __builtin_rotateright8, __builtin_rotateright16, __builtin_rotateright32 and __builtin_rotateright64 may now be used within constant expressions. New Compiler Flags … AArch64 options -moutline-atomics, -mno-outline-atomics to enable and disable calls to helper functions implementing atomic operations. These out-of-line helpers like ‘__aarch64_cas8_relax’ will detect at runtime AArch64 Large System Extensions (LSE) availability and either use their atomic instructions, or falls back to LL/SC loop. These options do not apply if the compilation target supports LSE. Atomic instructions are used directly in that case. The option’s behaviour mirrors GCC, the helpers are implemented both in compiler-rt and libgcc. New option -fbinutils-version= specifies the targeted binutils version. For example, -fbinutils-version=2.35 means compatibility with GNU as/ld before 2.35 is not needed: new features can be used and there is no need to work around old GNU as/ld bugs. Deprecated Compiler Flags The following options are deprecated and ignored. They will be removed in future versions of Clang. The clang-cl /fallback flag, which made clang-cl invoke Microsoft Visual C++ on files it couldn’t compile itself, has been deprecated. It will be removed in Clang 13. … Modified Compiler Flags On ELF, -gz now defaults to -gz=zlib with the integrated assembler. It produces SHF_COMPRESSED style compression of debug information. GNU binutils 2.26 or newer, or lld is required to link produced object files. Use -gz=zlib-gnu to get the old behavior. Now that this pointers are tagged with nonnull and dereferenceable(N), -fno-delete-null-pointer-checks has gained the power to remove the nonnull attribute on this for configurations that need it to be nullable. -gsplit-dwarf no longer implies -g2. -fasynchronous-unwind-tables is now the default on Linux AArch64/PowerPC. This behavior matches newer GCC. (D91760) (D92054) Support has been added for the following processors (command-line identifiers in parentheses): Arm Cortex-A78C (cortex-a78c). Arm Cortex-R82 (cortex-r82). Arm Neoverse V1 (neoverse-v1). Arm Neoverse N2 (neoverse-n2). Fujitsu A64FX (a64fx). For example, to select architecture support and tuning for Neoverse-V1 based systems, use -mcpu=neoverse-v1. Removed Compiler Flags The following options no longer exist. clang-cl’s /Zd flag no longer exist. But -gline-tables-only still exists and does the same thing. New Pragmas in Clang … Modified Pragmas in Clang The “#pragma clang loop vectorize_width” has been extended to support an optional ‘fixed|scalable’ argument, which can be used to indicate that the compiler should use fixed-width or scalable vectorization. Fixed-width is assumed by default. Scalable or vector length agnostic vectorization is an experimental feature for targets that support scalable vectors. For more information please refer to the Clang Language Extensions documentation. Attribute Changes in Clang Added support for the C++20 likelihood attributes [[likely]] and [[unlikely]]. As an extension they can be used in C++11 and newer. This extension is enabled by default.
clang: build with static analizer (default and needed for clang-tools-extra); remove clang-static-analyzer
clang: better PLIST
clang: updated to 10.0.0 What’s New in Clang 10.0.0? Some of the major new features and improvements to Clang are listed here. Generic improvements to Clang as a whole or to its underlying infrastructure are described first, followed by language-specific sections with improvements to Clang’s support for those languages. Major New Features clang used to run the actual compilation in a subprocess (“clang -cc1”). Now compilations are done in-process by default. -fno-integrated-cc1 restores the former behavior. The -v and -### flags will print “(in-process)” when compilations are done in-process. Concepts support. Clang now supports C++2a Concepts under the -std=c++2a flag. Improvements to Clang’s diagnostics -Wtautological-overlap-compare will warn on negative numbers and non-int types. -Wtautological-compare for self comparisons and -Wtautological-overlap-compare will now look through member and array access to determine if two operand expressions are the same. -Wtautological-bitwise-compare is a new warning group. This group has the current warning which diagnoses the tautological comparison of a bitwise operation and a constant. The group also has the new warning which diagnoses when a bitwise-or with a non-negative value is converted to a bool, since that bool will always be true. -Wbitwise-conditional-parentheses will warn on operator precedence issues when mixing bitwise-and (&) and bitwise-or (|) operator with the conditional operator (?:). -Wrange-loop-analysis got several improvements. It no longer warns about a copy being made when the result is bound to an rvalue reference. It no longer warns when an object of a small, trivially copyable type is copied. The warning now offers fix-its. Excluding -Wrange-loop-bind-reference it is now part of -Wall. To reduce the number of false positives the diagnostic is disabled in macros and template instantiations. -Wmisleading-indentation has been added. This warning is similar to the GCC warning of the same name. It warns about statements that are indented as if they were part of a if/else/for/while statement but are not semantically part of that if/else/for/while. -Wbitwise-op-parentheses and -Wlogical-op-parentheses are disabled by default. The new warnings -Wc99-designator and -Wreorder-init-list warn about uses of C99 initializers in C++ mode for cases that are valid in C99 but not in C++20. The new warning -Wsizeof-array-div catches cases like int arr[10]; ...sizeof(arr) / sizeof(short)... (should be sizeof(arr) / sizeof(int)), and the existing warning -Wsizeof-pointer-div catches more cases. The new warning -Wxor-used-as-pow warns on cases where it looks like the xor operator ^ is used to be mean exponentiation, e.g. 2 ^ 16. The new warning -Wfinal-dtor-non-final-class warns on classes that have a final destructor but aren’t themselves marked final. -Wextra now enables -Wdeprecated-copy. The warning deprecates move and copy constructors in classes where an explicit destructor is declared. This is for compatibility with GCC 9, and forward looking for a change that’s being considered for C++23. You can disable it with -Wno-deprecated-copy. Non-comprehensive list of changes in this release In both C and C++ (C17 6.5.6p8, C++ [expr.add]), pointer arithmetic is only permitted within arrays. In particular, the behavior of a program is not defined if it adds a non-zero offset (or in C, any offset) to a null pointer, or if it forms a null pointer by subtracting an integer from a non-null pointer, and the LLVM optimizer now uses those guarantees for transformations. This may lead to unintended behavior in code that performs these operations. The Undefined Behavior Sanitizer -fsanitize=pointer-overflow check has been extended to detect these cases, so that code relying on them can be detected and fixed. The Implicit Conversion Sanitizer (-fsanitize=implicit-conversion) has learned to sanitize pre/post increment/decrement of types with bit width smaller than int. For X86 target, -march=skylake-avx512, -march=icelake-client, -march=icelake-server, -march=cascadelake, -march=cooperlake will default to not using 512-bit zmm registers in vectorized code unless 512-bit intrinsics are used in the source code. 512-bit operations are known to cause the CPUs to run at a lower frequency which can impact performance. This behavior can be changed by passing -mprefer-vector-width=512 on the command line. Clang now defaults to .init_array on Linux. It used to use .ctors if the found GCC installation is older than 4.7.0. Add -fno-use-init-array to get the old behavior (.ctors). The behavior of the flag -flax-vector-conversions has been modified to more closely match GCC, as described below. In Clang 10 onwards, command lines specifying this flag do not permit implicit vector bitcasts between integer vectors and floating-point vectors. Such conversions are still permitted by default, however, and the default can be explicitly requested with the Clang-specific flag -flax-vector-conversions=all. In a future release of Clang, we intend to change the default to -fno-lax-vector-conversions. Improved support for octeon MIPS-family CPU. Added octeon+ to the list of of CPUs accepted by the driver. For the WebAssembly target, the wasm-opt tool will now be run if it is found in the PATH, which can reduce code size. For the RISC-V target, floating point registers can now be used in inline assembly constraints. New Compiler Flags The -fgnuc-version= flag now controls the value of __GNUC__ and related macros. This flag does not enable or disable any GCC extensions implemented in Clang. Setting the version to zero causes Clang to leave __GNUC__ and other GNU-namespaced macros, such as __GXX_WEAK__, undefined. vzeroupper insertion on X86 targets can now be disabled with -mno-vzeroupper. You can also force vzeroupper insertion to be used on CPUs that normally wouldn’t with -mvzeroupper. The -fno-concept-satisfaction-caching can be used to disable caching for satisfactions of Concepts. The C++2a draft standard does not currently permit this caching, but disabling it may incur significant compile-time costs. This flag is intended for experimentation purposes and may be removed at any time; please let us know if you encounter a situation where you need to specify this flag for correct program behavior. The -ffixed-xX flags now work on RISC-V. These reserve the corresponding general-purpose registers. RISC-V has added -mcmodel=medany and -mcmodel=medlow as aliases for -mcmodel=small and -mcmodel=medium respectively. Preprocessor definitions for __riscv_cmodel_medlow and __riscv_cmodel_medany have been corrected. -fmacro-prefix-map=OLD=NEW substitutes directory prefix OLD for NEW in predefined preprocessor macros such as __FILE__. This helps with reproducible builds that are location independent. The new -ffile-prefix-map option is equivalent to specifying both -fdebug-prefix-map and -fmacro-prefix-map. -fpatchable-function-entry=N[,M] is added to generate M NOPs before the function entry and N-M NOPs after the function entry. This is used by AArch64 ftrace in the Linux kernel. -mbranches-within-32B-boundaries is added as an x86 assembler mitigation for Intel’s Jump Condition Code Erratum. Deprecated Compiler Flags The following options are deprecated and ignored. They will be removed in future versions of Clang. -mmpx used to enable the __MPX__ preprocessor define for the Intel MPX instructions. There were no MPX intrinsics. -mno-mpx used to disable -mmpx and is the default behavior. -fconcepts-ts previously used to enable experimental concepts support. Use -std=c++2a instead to enable Concepts support. Modified Compiler Flags RISC-V now sets the architecture (riscv32/riscv64) based on the value provided to the -march flag, overriding the target provided by -triple. -flax-vector-conversions has been split into three different levels of laxness, and has been updated to match the GCC semantics: -flax-vector-conversions=all: This is Clang’s current default, and permits implicit vector conversions (performed as bitcasts) between any two vector types of the same overall bit-width. Former synonym: -flax-vector-conversions (Clang <= 9). -flax-vector-conversions=integer: This permits implicit vector conversions (performed as bitcasts) between any two integer vector types of the same overall bit-width. Synonym: -flax-vector-conversions (Clang >= 10). -flax-vector-conversions=none: Do not perform any implicit bitcasts between vector types. Synonym: -fno-lax-vector-conversions. -debug-info-kind now has an option -debug-info-kind=constructor, which is one level below -debug-info-kind=limited. This option causes debug info for classes to be emitted only when a constructor is emitted. RISC-V now chooses a slightly different sysroot path and defaults to using compiler-rt if no GCC installation is detected. RISC-V now supports multilibs in baremetal environments. This support does not extend to supporting multilib aliases. Attribute Changes in Clang Support was added for function __attribute__((target("branch-protection=...")))
clang: updated to 9.0.0 9.0.0: Major New Features * Experimental support for C++ for OpenCL has been added. Non-comprehensive list of changes in this release * The __VERSION__ macro has been updated. Previously this macro contained the string ‘4.2.1 Compatible’ to achieve compatibility with GCC 4.2.1, but that should no longer be necessary. However, to retrieve Clang’s version, please favor the one of the macro defined in clang namespaced version macros. New Compiler Flags * -ftime-trace and ftime-trace-granularity=N Emits flame chart style compilation time report in chrome://tracing and speedscope.app compatible format. A trace .json file is written next to the compiled object file, containing hierarchical time information about frontend activities (file parsing, template instantiation) and backend activities (modules and functions being optimized, optimization passes). Modified Compiler Flags * clang -dumpversion now returns the version of Clang itself. Windows Support * clang-cl now treats non-existent files as possible typos for flags, clang-cl /diagnostic:caret /c test.cc for example now produces clang: error: no such file or directory: '/diagnostic:caret'; did you mean '/diagnostics:caret'? * clang now parses the __declspec(allocator) specifier and generates debug information, so that memory usage can be tracked in Visual Studio. * The -print-search-dirs option now separates elements with semicolons, as is the norm for path lists on Windows * Improved handling of dllexport in conjunction with explicit template instantiations for MinGW, to allow building a shared libc++ for MinGW without --export-all-symbols to override the dllexport attributes
clang: updated to 8.0.0 Clang 8.0.0: Major New Features * Clang supports use of a profile remapping file, which permits profile data captured for one version of a program to be applied when building another version where symbols have changed (for example, due to renaming a class or namespace). See the UsersManual for details. * Clang has new options to initialize automatic variables with a pattern. The default is still that automatic variables are uninitialized. This isn’t meant to change the semantics of C and C++. Rather, it’s meant to be a last resort when programmers inadvertently have some undefined behavior in their code. These options aim to make undefined behavior hurt less, which security-minded people will be very happy about. * Improvements to Clang’s diagnostics Non-comprehensive list of changes in this release * The experimental feature Pretokenized Headers (PTH) was removed in its entirely from Clang. The feature did not properly work with about 1/3 of the possible tokens available and was unmaintained. * The internals of libc++ include directory detection on MacOS have changed. Instead of running a search based on the -resource-dir flag, the search is now based on the path of the compiler in the filesystem. The default behaviour should not change. However, if you override -resource-dir manually and rely on the old behaviour you will need to add appropriate compiler flags for finding the corresponding libc++ include directory. * The integrated assembler is used now by default for all MIPS targets. * Improved support for MIPS N32 ABI and MIPS R6 target triples. * Clang now includes builtin functions for bitwise rotation of common value sizes, such as: __builtin_rotateleft32 * Improved optimization for the corresponding MSVC compatibility builtins such as _rotl().
llvm: updated to 7.0.0 LLVM 7.0.0 Release The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets, improved PCH support in clang-cl, preliminary DWARF v5 support, basic support for OpenMP 4.5 offloading to NVPTX, OpenCL C++ support, MSan, X-Ray and libFuzzer support for FreeBSD, early UBSan, X-Ray and libFuzzer support for OpenBSD, UBSan checks for implicit conversions, many long-tail compatibility issues fixed in lld which is now production ready for ELF, COFF and MinGW, new tools llvm-exegesis, llvm-mca and diagtool. And as usual, many optimizations, improved diagnostics, and bug fixes. For more details, see the release notes: https://llvm.org/releases/7.0.0/docs/ReleaseNotes.html https://llvm.org/releases/7.0.0/tools/clang/docs/ReleaseNotes.html https://llvm.org/releases/7.0.0/tools/clang/tools/extra/docs/ReleaseNotes.html https://llvm.org/releases/7.0.0/tools/lld/docs/ReleaseNotes.html
llvm: updated to 6.0.1 6.0.1: Non-comprehensive list of changes in this release Support for retpolines was added to help mitigate “branch target injection” (variant 2) of the “Spectre” speculative side channels described by Project Zero and the Spectre paper. The Redirects argument of llvm::sys::ExecuteAndWait and llvm::sys::ExecuteNoWait was changed to an ArrayRef of optional StringRef‘s to make it safer and more convenient to use. The backend name was added to the Target Registry to allow run-time information to be fed back into TableGen. Out-of-tree targets will need to add the name used in the def X : Target definition to the call to RegisterTarget. The Debugify pass was added to opt to facilitate testing of debug info preservation. This pass attaches synthetic DILocations and DIVariables to the instructions in a Module. The CheckDebugify pass determines how much of the metadata is lost. Significantly improved quality of CodeView debug info for Windows. Preliminary support for Sanitizers and sibling features on X86(_64) NetBSD (ASan, UBsan, TSan, MSan, SafeStack, libFuzzer). Changes to the LLVM IR ---------------------- The fast-math-flags (FMF) have been updated. Previously, the ‘fast’ flag indicated that floating-point reassociation was allowed and all other flags were set too. The ‘fast’ flag still exists, but there is a new flag called ‘reassoc’ to indicate specifically that reassociation is allowed. A new bit called ‘afn’ was also added to selectively allow approximations for common mathlib functions like square-root. The new flags provide more flexibility to enable/disable specific floating-point optimizations. Making the optimizer respond appropriately to these flags is an ongoing effort. Changes to the AArch64 Target ----------------------------- Enabled the new GlobalISel instruction selection framework by default at -O0. Changes to the ARM Target ------------------------- Support for enabling SjLj exception handling on platforms where it isn’t the default. Changes to the Hexagon Target ----------------------------- The Hexagon backend now supports V65 ISA. The -mhvx option now takes an optional value that specifies the ISA version of the HVX coprocessor. The available values are v60, v62 and v65. By default, the value is set to be the same as the CPU version. The compiler option -mhvx-double is deprecated and will be removed in the next release of the compiler. Programmers should use the -mhvx-length option to specify the desired vector length: -mhvx-length=64b for 64-byte vectors and -mhvx-length=128b for 128-byte vectors. While the current default vector length is 64 bytes, users should always specify the length explicitly, since the default value may change in the future. The target feature hvx-double is deprecated and will be removed in the next release. LLVM IR generators should use target features hvx-length64b and hvx-length128b to indicate the vector length. The length should always be specified when HVX code generation is enabled. Changes to the MIPS Target -------------------------- Fixed numerous bugs: fpowi on MIPS64 giving incorrect results when used with a negative integer. Usage of the asm ‘c’ constraint with the wrong datatype causing an assert/crash. Fixed a conversion bug when using the DSP ASE. Fixed an inconsistency where objects were not marked as using the microMIPS as when the micromips function attribute or the ”.set micromips” directive was used. Reordered the MIPSR6 specific hazard scheduler pass to after the delay slot filler, fixing a class of rare edge case bugs where the delay slot filler would violate ISA restrictions. Fixed a crash when using a type of unknown size with gp relative addressing. Corrected the j macro for microMIPS. Corrected the encoding of movep for microMIPS32r6. Fixed an issue with the usage of insert instructions having an invalid set of operands. Fixed an issue where TLS symbols were not marked as such. Enabled the usage of register scavenging with MSA, due to its shorter offsets for loads and stores. Corrected the ELF headers when using the DSP ASE. New features: The long branch pass now generates some R6 specific instructions when targeting MIPSR6. The delay slot filler now performs more branch conversions if delay slots cannot be filled. The MIPS MT ASE is now fully supported. Added support for the lapc pseudo instruction. Improved the selection of multiple instructions (dext, nmadd, nmsub). Further improved microMIPS codesize reduction. Deprecation notices: microMIPS64R6 support was been deprecated since 5.0, and has now been completely removed. Changes to the SystemZ Target ----------------------------- During this release the SystemZ target has: Added support for 128-bit atomic operations. Added support for the “o” constraint for inline asm statements. Changes to the X86 Target ------------------------- During this release the X86 target has: Added support for enabling SjLj exception handling on platforms where it isn’t the default. Added intrinsics for Intel Extensions: VAES, GFNI, VPCLMULQDQ, AVX512VBMI2, AVX512BITALG, AVX512VNNI. Added support for Intel Icelake CPU. Fixed some X87 codegen bugs. Added instruction scheduling information for Intel Sandy Bridge, Ivy Bridge, Haswell, Broadwell, and Skylake CPUs. Improved scheduler model for AMD Jaguar CPUs. Improved llvm-mc’s disassembler for some EVEX encoded instructions. Add support for i8 and i16 vector signed/unsigned min/max horizontal reductions. Improved codegen for memory comparisons Improved codegen for i32 vector multiplies Improved codegen for scalar integer absolute values Improved codegen for vector integer rotations (XOP and AVX512) Improved codegen of data being transferred between GPRs and K-registers. Improved codegen for vector truncations. Improved folding of address computations into gather/scatter instructions. Gained initial support recognizing variable shuffles from vector element extracts and inserts. Improved documentation for SSE/AVX intrinsics in intrin.h header files. Gained support for emitting retpolines, including automatic insertion of the necessary thunks or using external thunks.
llvm: updated to 5.0.1 LLVM 5.0.1: This release contains bug-fixes for the LLVM 5.0.0 release. This release is API and ABI compatible with 5.0.0.
llvm: updated to 5.0.0 5.0.0: Non-comprehensive list of changes in this release * LLVM’s WeakVH has been renamed to WeakTrackingVH and a new WeakVH has been introduced. The new WeakVH nulls itself out on deletion, but does not track values across RAUW. * A new library named BinaryFormat has been created which holds a collection of code which previously lived in Support. This includes the file_magic structure and identify_magic functions, as well as all the structure and type definitions for DWARF, ELF, COFF, WASM, and MachO file formats. * The tool llvm-pdbdump has been renamed llvm-pdbutil to better reflect its nature as a general purpose PDB manipulation / diagnostics tool that does more than just dumping contents. * The BBVectorize pass has been removed. It was fully replaced and no longer used back in 2014 but we didn’t get around to removing it. Now it is gone. The SLP vectorizer is the suggested non-loop vectorization pass. * A new tool opt-viewer.py has been added to visualize optimization remarks in HTML. The tool processes the YAML files produced by clang with the -fsave-optimization-record option. * A new CMake macro LLVM_REVERSE_ITERATION has been added. If enabled, all supported unordered LLVM containers would be iterated in reverse order. This is useful for uncovering non-determinism caused by iteration of unordered containers. Currently, it supports reverse iteration of SmallPtrSet and DenseMap. * A new tool llvm-dlltool has been added to create short import libraries from GNU style definition files. The tool utilizes the PE COFF SPEC Import Library Format and PE COFF Auxiliary Weak Externals Format to achieve compatibility with LLD and MSVC LINK.
LLVM 4.0.0: The minimum compiler version required for building LLVM has been raised to 4.8 for GCC and 2015 for Visual Studio. The C API functions LLVMAddFunctionAttr, LLVMGetFunctionAttr, LLVMRemoveFunctionAttr, LLVMAddAttribute, LLVMRemoveAttribute, LLVMGetAttribute, LLVMAddInstrAttribute and LLVMRemoveInstrAttribute have been removed. The C API enum LLVMAttribute has been deleted. The definition and uses of LLVM_ATRIBUTE_UNUSED_RESULT in the LLVM source were replaced with LLVM_NODISCARD, which matches the C++17 [[nodiscard]] semantics rather than gcc’s __attribute__((warn_unused_result)). The Timer related APIs now expect a Name and Description. When upgrading code the previously used names should become descriptions and a short name in the style of a programming language identifier should be added. LLVM now handles invariant.group across different basic blocks, which makes it possible to devirtualize virtual calls inside loops. The aggressive dead code elimination phase (“adce”) now removes branches which do not effect program behavior. Loops are retained by default since they may be infinite but these can also be removed with LLVM option -adce-remove-loops when the loop body otherwise has no live operations. The llvm-cov tool can now export coverage data as json. Its html output mode has also improved.
Changes 3.9.1: The LLVMContext gains a new runtime check (see LLVMContext::discardValueNames()) that can be set to discard Value names (other than GlobalValue). This is intended to be used in release builds by clients that are interested in saving CPU/memory as much as possible. There is no longer a “global context” available in LLVM, except for the C API. The autoconf build system has been removed in favor of CMake. LLVM 3.9 requires CMake 3.4.3 or later to build. For information about using CMake please see the documentation on Building LLVM with CMake. For information about the CMake language there is also a CMake Primer document available. C API functions LLVMParseBitcode, LLVMParseBitcodeInContext, LLVMGetBitcodeModuleInContext and LLVMGetBitcodeModule having been removed. LLVMGetTargetMachineData has been removed (use LLVMGetDataLayout instead). The C API function LLVMLinkModules has been removed. The C API function LLVMAddTargetData has been removed. The C API function LLVMGetDataLayout is deprecated in favor of LLVMGetDataLayoutStr. The C API enum LLVMAttribute and associated API is deprecated in favor of the new LLVMAttributeRef API. The deprecated functions are LLVMAddFunctionAttr, LLVMAddTargetDependentFunctionAttr, LLVMRemoveFunctionAttr, LLVMGetFunctionAttr, LLVMAddAttribute, LLVMRemoveAttribute, LLVMGetAttribute, LLVMAddInstrAttribute, LLVMRemoveInstrAttribute and LLVMSetInstrParamAlignment. TargetFrameLowering::eliminateCallFramePseudoInstr now returns an iterator to the next instruction instead of void. Targets that previously did MBB.erase(I); return; now probably want return MBB.erase(I);. SelectionDAGISel::Select now returns void. Out-of-tree targets will need to be updated to replace the argument node and remove any dead nodes in cases where they currently return an SDNode * from this interface. Added the MemorySSA analysis, which hopes to replace MemoryDependenceAnalysis. It should provide higher-quality results than MemDep, and be algorithmically faster than MemDep. Currently, GVNHoist (which is off by default) makes use of MemorySSA. The minimum density for lowering switches with jump tables has been reduced from 40% to 10% for functions which are not marked optsize (that is, compiled with -Os).
Update llvm packages to 3.9.0 * Drop CppBackend. It is removed. Changelog: * GCC ABI Tag * LLVM IR: new intrinsics etc. * Change LLVM IPO model * Support ThinLTO * Improve the ARM targets, ARMv8.2-A support etc. * Improve the MIPS targets * Improve the PowerPC target, default optim O3 to O2 * Improve the X86 target, SKylake AVX-512 etc. * Improve the AMDGPU, better support for Mesa 12
Update to clang-3.8.0. Split out llvm tools to lang/llvm. Packaged in pkgsrc-wip by myself and Kamil. Remove stale pkgsrc/SunOS bread crumbs that were difficult to merge following the build framework switch. Needs to be redone. (Sorry!) Summary of significant changes in LLVM: - switch build framework from autoconf to CMake - llvm-ar now supports thin archives. - llvm doesn t produce .data.rel.ro.local or .data.rel sections anymore. - opional support for linking clang and the LLVM tools with a single libLLVM shared library pkgsrc note: we have this library in lang/libLLVM, but we don't currently use it. We may do so in the future if/when the API matures. - The optimization to move the prologue and epilogue of functions in colder code path (shrink-wrapping) is now enabled by default - new target-independent gcc-compatible emulated Thread Local Storage mode - various target specific optimizations Summary of significant changes in Clang: - new compiler flags for tuning what DWARF information is included - better strict alignment handling - better support for __builtin_object_size
Update to clang-3.7.0 and libLLVM-3.7.0 Compacted version of upstream's release notes: The LLVM C API LLVMGetTargetMachineData is deprecated DataLayout is no longer optional Comdats are now ortogonal to the linkage On ELF now supports multiple sections with the same name and comdat LLVM now lazily loads metadata in some cases Creating archives with IR files with debug info is now 25X faster llvm-ar(1) can create archives in the BSD format used by OS X LLVM received a backend for the extended Berkely Packet Filter instruction set The BPF target is now available by default Switch-case lowering was rewritten to avoid generating unbalanced search trees The debug info IR class hierarchy now inherits from Metadata Argument-less TargetMachine::getSubtarget has been removed from the tree
Makefile: move some stuff from Makefile.common here PLIST: unsubstitute ${MACHINE_ARCH}
Update to clang-3.6.0 (2015-02-27) Non-comprehensive list of changes in this release: - Support for AuroraUX has been removed. - Added support for a native object file-based bitcode wrapper format. - Added support for MSVC?s __vectorcall calling convention as x86_vectorcallcc.
Changes 3.5.0: All backends have been changed to use the MC asm printer and support for the non MC one has been removed. Clang can now successfully self-host itself on Linux/Sparc64 and on FreeBSD/Sparc64. LLVM now assumes the assembler supports .loc for generating debug line numbers. The old support for printing the debug line info directly was only used by llc and has been removed. All inline assembly is parsed by the integrated assembler when it is enabled. Previously this was only the case for object-file output. It is now the case for assembly output as well. The integrated assembler can be disabled with the -no-integrated-as option. llvm-ar now handles IR files like regular object files. In particular, a regular symbol table is created for symbols defined in IR files, including those in file scope inline assembly. LLVM now always uses cfi directives for producing most stack unwinding information. The prefix for loop vectorizer hint metadata has been changed from llvm.vectorizer to llvm.loop.vectorize. In addition, llvm.vectorizer.unroll metadata has been renamed llvm.loop.interleave.count. Some backends previously implemented Atomic NAND(x,y) as x & ~y. Now all backends implement it as ~(x & y), matching the semantics of GCC 4.4 and later.
Changes 3.4.1: Various bug fixes for AArch64, ARM, PowerPC, R600, and X86 targets. R600 geometry shader support Fix for vaargs on X86
Added libc++
Fix library extension on Darwin
Update to 3.4 * Tested under NetBSD/amd64 6.99.28 and Debian GNU/Linux/amd64 7.3 Changelog: From: http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_34/final/docs/ReleaseNotes.rst Non-comprehensive list of changes in this release ================================================= * This is expected to be the last release of LLVM which compiles using a C++98 toolchain. We expect to start using some C++11 features in LLVM and other sub-projects starting after this release. That said, we are committed to supporting a reasonable set of modern C++ toolchains as the host compiler on all of the platforms. This will at least include Visual Studio 2012 on Windows, and Clang 3.1 or GCC 4.7.x on Mac and Linux. The final set of compilers (and the C++11 features they support) is not set in stone, but we wanted users of LLVM to have a heads up that the next release will involve a substantial change in the host toolchain requirements. * The regression tests now fail if any command in a pipe fails. To disable it in a directory, just add ``config.pipefail = False`` to its ``lit.local.cfg``. See :doc:`Lit <CommandGuide/lit>` for the details. * Support for exception handling has been removed from the old JIT. Use MCJIT if you need EH support. * The R600 backend is not marked experimental anymore and is built by default. * ``APFloat::isNormal()`` was renamed to ``APFloat::isFiniteNonZero()`` and ``APFloat::isIEEENormal()`` was renamed to ``APFloat::isNormal()``. This ensures that ``APFloat::isNormal()`` conforms to IEEE-754R-2008. * The library call simplification pass has been removed. Its functionality has been integrated into the instruction combiner and function attribute marking passes. * Support for building using Visual Studio 2008 has been dropped. Use VS 2010 or later instead. For more information, see the `Getting Started using Visual Studio <GettingStartedVS.html>`_ page. * The Loop Vectorizer that was previously enabled for ``-O3`` is now enabled for ``-Os`` and ``-O2``. * The new SLP Vectorizer is now enabled by default. * ``llvm-ar`` now uses the new Object library and produces archives and symbol tables in the gnu format. * FileCheck now allows specifing ``-check-prefix`` multiple times. This helps reduce duplicate check lines when using multiple RUN lines. * The bitcast instruction no longer allows casting between pointers with different address spaces. To achieve this, use the new addrspacecast instruction. * Different sized pointers for different address spaces should now generally work. This is primarily useful for GPU targets. * OCaml bindings have been significantly extended to cover almost all of the LLVM libraries. Mips Target ----------- Support for the MIPS SIMD Architecture (MSA) has been added. MSA is supported through inline assembly, intrinsics with the prefix '``__builtin_msa``', and normal code generation. For more information on MSA (including documentation for the instruction set), see the `MIPS SIMD page at Imagination Technologies <http://imgtec.com/mips/mips-simd.asp>`_ PowerPC Target -------------- Changes in the PowerPC backend include: * fast-isel support (for faster ``-O0`` code generation) * many improvements to the builtin assembler * support for generating unaligned (Altivec) vector loads * support for generating the fcpsgn instruction * generate ``frin`` for ``round()`` (not ``nearbyint()`` and ``rint()``, which had been done only in fast-math mode) * improved instruction scheduling for embedded cores (such as the A2) * improved prologue/epilogue generation (especially in 32-bit mode) * support for dynamic stack alignment (and dynamic stack allocations with large alignments) * improved generation of counter-register-based loops * bug fixes SPARC Target ------------ The SPARC backend got many improvements, namely * experimental SPARC V9 backend * JIT support for SPARC * fp128 support * exception handling * TLS support * leaf functions optimization * bug fixes SystemZ/s390x Backend --------------------- LLVM and clang can now optimize for zEnterprise z196 and zEnterprise EC12 targets. In clang these targets are selected using ``-march=z196`` and ``-march=zEC12`` respectively. From: http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_34/final/docs/ReleaseNotes.rst What's New in Clang 3.4? ======================== Some of the major new features and improvements to Clang are listed here. Generic improvements to Clang as a whole or to its underlying infrastructure are described first, followed by language-specific sections with improvements to Clang's support for those languages. Last release which will build as C++98 -------------------------------------- This is expected to be the last release of Clang which compiles using a C++98 toolchain. We expect to start using some C++11 features in Clang starting after this release. That said, we are committed to supporting a reasonable set of modern C++ toolchains as the host compiler on all of the platforms. This will at least include Visual Studio 2012 on Windows, and Clang 3.1 or GCC 4.7.x on Mac and Linux. The final set of compilers (and the C++11 features they support) is not set in stone, but we wanted users of Clang to have a heads up that the next release will involve a substantial change in the host toolchain requirements. Note that this change is part of a change for the entire LLVM project, not just Clang. Major New Features ------------------ Improvements to Clang's diagnostics ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Clang's diagnostics are constantly being improved to catch more issues, explain them more clearly, and provide more accurate source information about them. The improvements since the 3.3 release include: - -Wheader-guard warns on mismatches between the #ifndef and #define lines in a header guard. .. code-block:: c #ifndef multiple #define multi #endif returns `warning: 'multiple' is used as a header guard here, followed by #define of a different macro [-Wheader-guard]` - -Wlogical-not-parentheses warns when a logical not ('!') only applies to the left-hand side of a comparison. This warning is part of -Wparentheses. .. code-block:: c++ int i1 = 0, i2 = 1; bool ret; ret = !i1 == i2; returns `warning: logical not is only applied to the left hand side of this comparison [-Wlogical-not-parentheses]` - Boolean increment, a deprecated feature, has own warning flag -Wdeprecated-increment-bool, and is still part of -Wdeprecated. - Clang errors on builtin enum increments and decrements. .. code-block:: c++ enum A { A1, A2 }; void test() { A a; a++; } returns `error: must use 'enum' tag to refer to type 'A'` - -Wloop-analysis now warns on for-loops which have the same increment or decrement in the loop header as the last statement in the loop. .. code-block:: c void foo(char *a, char *b, unsigned c) { for (unsigned i = 0; i < c; ++i) { a[i] = b[i]; ++i; } } returns `warning: variable 'i' is incremented both in the loop header and in the loop body [-Wloop-analysis]` - -Wuninitialized now performs checking across field initializers to detect when one field in used uninitialized in another field initialization. .. code-block:: c++ class A { int x; int y; A() : x(y) {} }; returns `warning: field 'y' is uninitialized when used here [-Wuninitialized]` - Clang can detect initializer list use inside a macro and suggest parentheses if possible to fix. - Many improvements to Clang's typo correction facilities, such as: + Adding global namespace qualifiers so that corrections can refer to shadowed or otherwise ambiguous or unreachable namespaces. + Including accessible class members in the set of typo correction candidates, so that corrections requiring a class name in the name specifier are now possible. + Allowing typo corrections that involve removing a name specifier. + In some situations, correcting function names when a function was given the wrong number of arguments, including situations where the original function name was correct but was shadowed by a lexically closer function with the same name yet took a different number of arguments. + Offering typo suggestions for 'using' declarations. + Providing better diagnostics and fixit suggestions in more situations when a '->' was used instead of '.' or vice versa. + Providing more relevant suggestions for typos followed by '.' or '='. + Various performance improvements when searching for typo correction candidates. - `LeakSanitizer <LeakSanitizer.html>`_ is an experimental memory leak detector which can be combined with AddressSanitizer. New Compiler Flags ------------------ - Clang no longer special cases -O4 to enable lto. Explicitly pass -flto to enable it. - Clang no longer fails on >= -O5. These flags are mapped to -O3 instead. - Command line "clang -O3 -flto a.c -c" and "clang -emit-llvm a.c -c" are no longer equivalent. - Clang now errors on unknown -m flags (``-munknown-to-clang``), unknown -f flags (``-funknown-to-clang``) and unknown options (``-what-is-this``). C Language Changes in Clang --------------------------- - Added new checked arithmetic builtins for security critical applications. C++ Language Changes in Clang ----------------------------- - Fixed an ABI regression, introduced in Clang 3.2, which affected member offsets for classes inheriting from certain classes with tail padding. See Bug16537. - Clang 3.4 supports the 2013-08-28 draft of the ISO WG21 SG10 feature test macro recommendations. These aim to provide a portable method to determine whether a compiler supports a language feature, much like Clang's |has_feature macro|_. .. |has_feature macro| replace:: ``__has_feature`` macro .. _has_feature macro: LanguageExtensions.html#has-feature-and-has-extension C++1y Feature Support ^^^^^^^^^^^^^^^^^^^^^ Clang 3.4 supports all the features in the current working draft of the upcoming C++ standard, provisionally named C++1y. Support for the following major new features has been added since Clang 3.3: - Generic lambdas and initialized lambda captures. - Deduced function return types (``auto f() { return 0; }``). - Generalized ``constexpr`` support (variable mutation and loops). - Variable templates and static data member templates. - Use of ``'`` as a digit separator in numeric literals. - Support for sized ``::operator delete`` functions. In addition, ``[[deprecated]]`` is now accepted as a synonym for Clang's existing ``deprecated`` attribute. Use ``-std=c++1y`` to enable C++1y mode. OpenCL C Language Changes in Clang ---------------------------------- - OpenCL C "long" now always has a size of 64 bit, and all OpenCL C types are aligned as specified in the OpenCL C standard. Also, "char" is now always signed. Internal API Changes -------------------- These are major API changes that have happened since the 3.3 release of Clang. If upgrading an external codebase that uses Clang as a library, this section should help get you past the largest hurdles of upgrading. Wide Character Types ^^^^^^^^^^^^^^^^^^^^ The ASTContext class now keeps track of two different types for wide character types: WCharTy and WideCharTy. WCharTy represents the built-in wchar_t type available in C++. WideCharTy is the type used for wide character literals; in C++ it is the same as WCharTy, but in C99, where wchar_t is a typedef, it is an integer type. Static Analyzer --------------- The static analyzer has been greatly improved. This impacts the overall analyzer quality and reduces a number of false positives. In particular, this release provides enhanced C++ support, reasoning about initializer lists, zeroing constructors, noreturn destructors and modeling of destructor calls on calls to delete. Clang Format ------------ Clang now includes a new tool ``clang-format`` which can be used to automatically format C, C++ and Objective-C source code. ``clang-format`` automatically chooses linebreaks and indentation and can be easily integrated into editors, IDEs and version control systems. It supports several pre-defined styles as well as precise style control using a multitude of formatting options. ``clang-format`` itself is just a thin wrapper around a library which can also be used directly from code refactoring and code translation tools. More information can be found on `Clang Format's site <http://clang.llvm.org/docs/ClangFormat.html>`_.
Changes 3.3: The CellSPU port has been removed. It can still be found in older versions. The IR-level extended linker APIs (for example, to link bitcode files out of archives) have been removed. Any existing clients of these features should move to using a linker with integrated LTO support. LLVM and Clang’s documentation has been migrated to the Sphinx documentation generation system which uses easy-to-write reStructuredText. See llvm/docs/README.txt for more information. TargetTransformInfo (TTI) is a new interface that can be used by IR-level passes to obtain target-specific information, such as the costs of instructions. Only “Lowering” passes such as LSR and the vectorizer are allowed to use the TTI infrastructure. We’ve improved the X86 and ARM cost model. The Attributes classes have been completely rewritten and expanded. They now support not only enumerated attributes and alignments, but “string” attributes, which are useful for passing information to code generation. See How To Use Attributes for more details. TableGen’s syntax for instruction selection patterns has been simplified. Instead of specifying types indirectly with register classes, you should now specify types directly in the input patterns. See SparcInstrInfo.td for examples of the new syntax. The old syntax using register classes still works, but it will be removed in a future LLVM release. MCJIT now supports exception handling. Support for it in the old jit will be removed in the 3.4 release. Command line options can now be grouped into categories which are shown in the output of -help. See Grouping options into categories. The appearance of command line options in -help that are inherited by linking with libraries that use the LLVM Command line support library can now be modified at runtime. See The cl::getRegisteredOptions function.
Changes 3.2: * Improvements to Clang's diagnostics * Support for tls_model attribute * Type safety attributes * Documentation comment support More...
Changes 3.1: * Major New Features - AddressSanitizer, a fast memory error detector. - MachineInstr Bundles, Support to model instruction bundling / packing. - ARM Integrated Assembler, A full featured assembler and direct-to-object support for ARM. - Basic Block Placement Probability driven basic block placement. * LLVM IR and Core Improvements - A new type representing 16 bit half floating point values has been added. - IR now supports vectors of pointers, including vector GEPs. - Module flags have been introduced. They convey information about the module as a whole to LLVM subsystems. This is currently used to encode Objective C ABI information. - Loads can now have range metadata attached to them to describe the possible values being loaded. - The llvm.ctlz and llvm.cttz intrinsics now have an additional argument which indicates whether the behavior of the intrinsic is undefined on a zero input. This can be used to generate more efficient code on platforms that only have instructions which don't return the type size when counting bits in 0. * Optimizer Improvements - The loop unroll pass now is able to unroll loops with run-time trip counts. This feature is turned off by default, and is enabled with the -unroll-runtime flag. - A new basic-block autovectorization pass is available. Pass -vectorize to run this pass along with some associated post-vectorization cleanup passes. For more information, see the EuroLLVM 2012 slides: Autovectorization with LLVM. - Inline cost heuristics have been completely overhauled and now closely model constant propagation through call sites, disregard trivially dead code costs, and can model C++ STL iterator patterns.
Removed wrong entry from PLIST
LLVM 3.0 includes several major changes and big features: * llvm-gcc is no longer supported, and not included in the release. We recommend switching to Clang or DragonEgg. * The linear scan register allocator has been replaced with a new "greedy" register allocator, enabling live range splitting and many other optimizations that lead to better code quality. Please see its blog post or its talk at the Developer Meeting for more information. * LLVM IR now includes full support for atomics memory operations intended to support the C++'11 and C'1x memory models. This includes atomic load and store, compare and exchange, and read/modify/write instructions as well as a full set of memory ordering constraints. Please see the Atomics Guide for more information. * The LLVM IR exception handling representation has been redesigned and reimplemented, making it more elegant, fixing a huge number of bugs, and enabling inlining and other optimizations. Please see its blog post and the Exception Handling documentation for more information. * The LLVM IR Type system has been redesigned and reimplemented, making it faster and solving some long-standing problems. Please see its blog post for more information. * The MIPS backend has made major leaps in this release, going from an experimental target to being virtually production quality and supporting a wide variety of MIPS subtargets. See the MIPS section below for more information. * The optimizer and code generator now supports gprof and gcov-style coverage and profiling information, and includes a new llvm-cov tool (but also works with gcov). Clang exposes coverage and profiling through GCC-compatible command line options.
LLVM 2.9 includes several major new capabilities: * Type Based Alias Analysis (TBAA) is now implemented and turned on by default in Clang. This allows substantially better load/store optimization in some cases. TBAA can be disabled by passing -fno-strict-aliasing. * This release has seen a continued focus on quality of debug information. LLVM now generates much higher fidelity debug information, particularly when debugging optimized code. * Inline assembly now supports multiple alternative constraints. * A new backend for the NVIDIA PTX virtual ISA (used to target its GPUs) is under rapid development. It is not generally useful in 2.9, but is making rapid progress.
Changes 2.8: * libc++ and LLDB are major new additions to the LLVM collective. * LLVM 2.8 now has pretty decent support for debugging optimized code. You should be able to reliably get debug info for function arguments, assuming that the value is actually available where you have stopped. * A new 'llvm-diff' tool is available that does a semantic diff of .ll files. * The MC subproject has made major progress in this release. Direct .o file writing support for darwin/x86[-64] is now reliable and support for other targets and object file formats are in progress. * The memcpy, memmove, and memset intrinsics now take address space qualified pointers and a bit to indicate whether the transfer is "volatile" or not. * Per-instruction debug info metadata is much faster and uses less memory by using the new DebugLoc class. * LLVM IR now has a more formalized concept of "trap values", which allow the optimizer to optimize more aggressively in the presence of undefined behavior, while still producing predictable results. * LLVM IR now supports two new linkage types (linker_private_weak and linker_private_weak_def_auto) which map onto some obscure MachO concepts. * The optimizer now has support for updating debug information as it goes. A key aspect of this is the new llvm.dbg.value intrinsic. This intrinsic represents debug info for variables that are promoted to SSA values (typically by mem2reg or the -scalarrepl passes). * The JumpThreading pass is now much more aggressive about implied value relations, allowing it to thread conditions like "a == 4" when a is known to be 13 in one of the predecessors of a block. It does this in conjunction with the new LazyValueInfo analysis pass. * The new RegionInfo analysis pass identifies single-entry single-exit regions in the CFG. You can play with it with the "opt -regions analyze" or "opt -view-regions" commands. * The loop optimizer has significantly improved strength reduction and analysis capabilities. Notably it is able to build on the trap value and signed integer overflow information to optimize <= and >= loops. * The CallGraphSCCPassManager now has some basic support for iterating within an SCC when a optimizer devirtualizes a function call. This allows inlining through indirect call sites that are devirtualized by store-load forwarding and other optimizations. * The new -loweratomic pass is available to lower atomic instructions into their non-atomic form. This can be useful to optimize generic code that expects to run in a single-threaded environment.
update to 2.7 many fixes and improvements, eg C++ support see the release notes for details
add clang-2.6, a C compiler based om LLVM, based on Adam Hoka's llvm pkg in pkgsrc-wip (This installs all the LLVM bits too, so it conflicts with a pure llvm pkg, but it is not easily separated.)
Initial revision