This project is mirrored from https://github.com/llvm/llvm-project.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- Apr 09, 2022
-
-
Bill Wendling authored
-
Aaron Ballman authored
This should speculatively fix build bots: https://lab.llvm.org/buildbot#builders/19/builds/10294 https://lab.llvm.org/buildbot#builders/37/builds/12289
-
Adrian Prantl authored
-
Kevin Athey authored
Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D122849
-
Paul Robinson authored
Simply returning will report the test as PASSED when it didn't really do anything. SKIPPED is the correct result for these. Found by the Rotten Green Tests project.
-
Richard authored
When a "keyword" token like __restrict was present in a macro condition, modernize-macro-to-enum would assert in non-release builds. However, even for a "keyword" token, calling getIdentifierInfo()->getName() would retrieve the text of the token, which is what we want. Our intention is to scan names that appear in conditional expressions in potential enum clusters and invalidate those clusters if they contain the name. Also, guard against "raw identifiers" appearing as potential enums. This shouldn't happen, but it doesn't hurt to generalize the code. Differential Revision: https://reviews.llvm.org/D123349 Fixes #54775
-
Jonas Devlieghere authored
XFAIL a series of tests that are failing remotely.
-
Jonas Devlieghere authored
Skip another batch of tests that don't really make sense to run remotely.
-
Bill Wendling authored
This is an attempt to fix a test failure on one of the buildbot Windows machines. It also turns all of the "ASSERT_" macros into "EXPECT_" to catch all other failures. Link: https://lab.llvm.org/buildbot/#/builders/216/builds/2647
-
Mitch Phillips authored
Differential Revision: https://reviews.llvm.org/D118948
-
Michael Jones authored
This patch adds the sequential mode implementation of the printf parser, as well as unit tests for it. In addition it adjusts the surrounding files to accomodate changes in the design found in the implementation process. Reviewed By: sivachandra Differential Revision: https://reviews.llvm.org/D123339
-
Louis Dionne authored
-
Nilay Vaish authored
This is to simplify the changes made in D122780. This diff was generated using the command: ``` clang-format include/__algorithm/sort.h -i ``` Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D122858
-
Gustavo Henrique Nihei authored
This patch addresses a clash with the PS register from Xtensa defined in the <specreg.h> header file, which is commonly included in OS implementation. Issue identified while building libc++ port for Apache NuttX, targeting Xtensa-based chips (e.g. Espressif's ESP32). Signed-off-by:
Gustavo Henrique Nihei <gustavo.nihei@espressif.com> Differential Revision: https://reviews.llvm.org/D122479
-
LLVM GN Syncbot authored
-
LLVM GN Syncbot authored
-
Aaron Ballman authored
Functions without prototypes in C (also known as K&R C functions) were introduced into C89 as a deprecated feature and C2x is now reclaiming that syntax space with different semantics. However, Clang's -Wstrict-prototypes diagnostic is off-by-default (even in pedantic mode) and does not suffice to warn users about issues in their code. This patch changes the behavior of -Wstrict-prototypes to only diagnose declarations and definitions which are not going to change behavior in C2x mode, and enables the diagnostic in -pedantic mode. The diagnostic is now specifically about the fact that the feature is deprecated. It also adds -Wdeprecated-non-prototype, which is grouped under -Wstrict-prototypes and diagnoses declarations or definitions which will change behavior in C2x mode. This diagnostic is enabled by default because the risk is higher for the user to continue to use the deprecated feature. Differential Revision: https://reviews.llvm.org/D122895
-
Aaron Ballman authored
This reverts commit 8aa14905. Broke testing: https://lab.llvm.org/buildbot/#/builders/109/builds/36233
-
Azat Khuzhin authored
GCC 12 reports: libcxx/include/string:727:13: error: anonymous struct with base classes 727 | : __padding<value_type> Differential Revision: https://reviews.llvm.org/D122598
-
Vang Thao authored
Enable the PreRARematerialize pass when there are multiple high RP scheduling regions present. Require the occupancy in all high RP regions be improved before finalizing sinking. If any high RP region did not improve in occupancy then un-do all sinking and restore the state to before the pass. Reviewed By: rampitec Differential Revision: https://reviews.llvm.org/D122501
-
Nicolai Hähnle authored
Highlights a gap in DAG-based ISel where we unnecessarily choose vector instructions. GlobalISel already looks good.
-
Connor Kuehl authored
The Randstruct feature is a compile-time hardening technique that randomizes the field layout for designated structures of a code base. Admittedly, this is mostly useful for closed-source releases of code, since the randomization seed would need to be available for public and open source applications. Why implement it? This patch set enhances Clang’s feature parity with that of GCC which already has the Randstruct feature. It's used by the Linux kernel in certain structures to help thwart attacks that depend on structure layouts in memory. This patch set is a from-scratch reimplementation of the Randstruct feature that was originally ported to GCC. The patches for the GCC implementation can be found here: https://www.openwall.com/lists/kernel-hardening/2017/04/06/14 Link: https://lists.llvm.org/pipermail/cfe-dev/2019-March/061607.html Co-authored-by:
Cole Nixon <nixontcole@gmail.com> Co-authored-by:
Connor Kuehl <cipkuehl@gmail.com> Co-authored-by:
James Foster <jafosterja@gmail.com> Co-authored-by:
Jeff Takahashi <jeffrey.takahashi@gmail.com> Co-authored-by:
Jordan Cantrell <jordan.cantrell@mail.com> Co-authored-by:
Nikk Forbus <nicholas.forbus@gmail.com> Co-authored-by:
Tim Pugh <nwtpugh@gmail.com> Co-authored-by:
Bill Wendling <isanbard@gmail.com> Signed-off-by:
Bill Wendling <isanbard@gmail.com> Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D121556
-
Fangrui Song authored
It has several problems like not-compilable weak attribute with MSVC (and the usage needs further scrutiny), and " different types for formal and actual parameter" https://lab.llvm.org/buildbot/#/builders/127/builds/27760/steps/7/logs/stdio This reverts commit 8843245d, 492c5c05, bf2dc4b3.
-
Paul Robinson authored
-
Valentin Clement authored
This patch avoids to fold `fir.box_addr` when the defining `fir.embox` op has a slice. If the op is folded the slice information are lost. This kind of problem occurred with code like: ``` call check(y(half+1:)) ``` where `y` is an array. Reviewed By: jeanPerier Differential Revision: https://reviews.llvm.org/D123392
-
Mitch Phillips authored
Currently, enablement of heap MTE on Android is specified by an ELF note, which signals to the linker to enable heap MTE. This change allows -fsanitize=memtag-heap to synthesize these notes, rather than adding them through the build system. We need to extend this feature to also signal the linker to do special work for MTE globals (in future) and MTE stack (currently implemented in the toolchain, but not implemented in the loader). Current Android uses a non-backwards-compatible ELF note, called ".note.android.memtag". Stack MTE is an ABI break anyway, so we don't mind that we won't be able to run executables with stack MTE on Android 11/12 devices. The current expectation is to support the verbiage used by Android, in that "SYNC" means MTE Synchronous mode, and "ASYNC" effectively means "fast", using the Kernel auto-upgrade feature that allows hardware-specific and core-specific configuration as to whether "ASYNC" would end up being Asynchronous, Asymmetric, or Synchronous on that particular core, whichever has a reasonable performance delta. Of course, this is platform and loader-specific. Differential Revision: https://reviews.llvm.org/D118948
-
wren romano authored
This reorganization helps to clean up the changes needed for D122060. Work towards fixing: https://github.com/llvm/llvm-project/issues/51652 Depends On D122625 Reviewed By: aartbik Differential Revision: https://reviews.llvm.org/D122928
-
Florian Hahn authored
This fixes the code to actually use the location of the instruction, if available. Previously, SetInsertPoint would overwrite the insert point set from the instruction.
-
Florian Hahn authored
-
Matt Arsenault authored
Fixes issue 47690. The reproduction steps produced a shared object from clang directly, and then fed the shared object back into lld. With no regular object files, this assert was hit. I'm not sure if we need to or should be looking for equivalent fields in shared objects.
-
Tue Ly authored
Make FMA flag checks more accurate for x86-64 targets, and refactor polyeval to use multiply and add instead when FMA instructions are not available. Reviewed By: michaelrj, sivachandra Differential Revision: https://reviews.llvm.org/D123335
-
Mark de Wever authored
This change is done to see whether all platforms have a CI with the Japanese locale installed. This wires in the locale in the tests and uses it in one test. This is a preparation for the tests of the chrono formatters. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D122738
-
Jorge Gorbe Moya authored
-
Jonas Devlieghere authored
Skip a bunch of tests that don't really make sense to run remotely.
-
Jonas Devlieghere authored
-
Jonas Devlieghere authored
We need to import foundation to get a 'NSLog' declaration when building against the iOS SDK. This doesn't appear necessary when building against the macOS SDK, presumable because it gets transitively imported by objc/NSObject.h
-
Jorge Gorbe Moya authored
-
Chris Bieneman authored
This document is a first-stab at addressing some of the questions about HLSL support in Clang. Differential Revision: https://reviews.llvm.org/D123278
-
Siu Chi Chan authored
Fix backward compatibility issue due to D120662. Change-Id: I7cd0f704aabbaac7dcf59fd4b73b4f0e0cdfa69f Reviewed By: yaxunl, saiislam Differential Revision: https://reviews.llvm.org/D123387
-
Arthur Eubanks authored
And thread DSE's ephemeral values to EarliestEscapeInfo. This allows more precise analysis in DSEState::isReadClobber() via BatchAA. Followup to D123162. Reviewed By: nikic Differential Revision: https://reviews.llvm.org/D123342
-