[all-commits] [llvm/llvm-project] d8a8ea: Revert "[libc++][string] Remove potential non-trai...
Florian Mayer via All-commits
all-commits at lists.llvm.org
Tue Sep 10 17:06:15 PDT 2024
Branch: refs/heads/users/fmayer/spr/hwasan-optimize-attrinfer-fix-for-selective-hwasan
Home: https://github.com/llvm/llvm-project
Commit: d8a8eae6daa6523b28526e2b8f65879e74858f68
https://github.com/llvm/llvm-project/commit/d8a8eae6daa6523b28526e2b8f65879e74858f68
Author: Daniel Thornburgh <dthorn at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M libcxx/include/string
Log Message:
-----------
Revert "[libc++][string] Remove potential non-trailing 0-length array" (#108091)
Reverts llvm/llvm-project#105865
This breaks a pair of LLDB tests in CI.
Commit: ce392471c0d9cb3ef88d05fcbcff59de8ea0c1e1
https://github.com/llvm/llvm-project/commit/ce392471c0d9cb3ef88d05fcbcff59de8ea0c1e1
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/include/flang/Semantics/type.h
M flang/lib/Evaluate/type.cpp
M flang/lib/Semantics/check-declarations.cpp
M flang/lib/Semantics/expression.cpp
M flang/lib/Semantics/type.cpp
A flang/test/Semantics/Inputs/modfile66.cuf
A flang/test/Semantics/modfile66.f90
Log Message:
-----------
[flang] Silence spurious error on non-CUDA use of CUDA module (#107444)
When a module file has been compiled with CUDA enabled, don't emit
spurious errors about non-interoperable types when that module is read
by a USE statement in a later non-CUDA compilation.
Commit: 5a229dbca19f5ad7ebd15c85b432cd54e70fd09a
https://github.com/llvm/llvm-project/commit/5a229dbca19f5ad7ebd15c85b432cd54e70fd09a
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/docs/Extensions.md
M flang/lib/Semantics/resolve-names.cpp
M flang/test/Semantics/resolve24.f90
Log Message:
-----------
[flang] Relax error into a warning (#107489)
The standard requires that a generic interface with the same name as a
derived type contain only functions. We generally allow a generic
interface to contain both functions and subroutines, since there's never
any ambiguity at the point of call; these is helpful when the specific
procedures of two generics are combined during USE association. Emit a
warning instead of a hard error when a generic interface with the same
name as a derived type contains a subroutine to improve portability of
code from compilers that don't check for this condition.
Commit: d2126ec1af543b23817c742c283ec441f21bf42b
https://github.com/llvm/llvm-project/commit/d2126ec1af543b23817c742c283ec441f21bf42b
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/include/flang/Evaluate/expression.h
M flang/include/flang/Evaluate/tools.h
M flang/lib/Evaluate/expression.cpp
M flang/lib/Evaluate/fold-implementation.h
A flang/test/Semantics/Inputs/modfile67.mod
A flang/test/Semantics/modfile67.f90
Log Message:
-----------
[flang] Fix bogus error about procedure incompatbility (#107645)
This was a subtle problem. When the shape of a function result is
explicit but not constant, it is characterized with bounds expressions
that use Extremum<SubscriptInteger> operations to force extents to 0
rather than be negative. These Extremum operations are formatted as
"max()" intrinsic functions in the module file. Upon being read from the
module file, they are not folded back into Extremum operations, but
remain as function references; and this then leads to expressions not
comparing equal when the procedure characteristics are compared to those
of a local procedure declared identically.
The real fix here would be for folding to just always change max and min
function references into Extremum<> operations, constant operands or
not, and I tried that, but it lead to test failures and crashes in
lowering that I couldn't resolve. So, until those can be fixed, here's a
change that will read max/min operations in module file declarations
back into Extremum operations to solve the compatibility checking
problem, but leave other non-constant max/min operations as function
calls.
Commit: fe58527305d86df8bd9770f3d41a6de420958af7
https://github.com/llvm/llvm-project/commit/fe58527305d86df8bd9770f3d41a6de420958af7
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/runtime/time-intrinsic.cpp
Log Message:
-----------
[flang] Relax ETIME(VALUES=) runtime checking (#107647)
Don't require the "VALUES=" argument to the extension intrinsic
procedure ETIME to have exactly two elements. Other compilers that
support ETIME do not, and it's easy to adapt the behavior to whatever
the dynamic size turns out to be.
Commit: 26ac30bcec71ae97ba740fb6cf473eac3ac37887
https://github.com/llvm/llvm-project/commit/26ac30bcec71ae97ba740fb6cf473eac3ac37887
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/docs/Extensions.md
M flang/include/flang/Common/Fortran-features.h
M flang/lib/Evaluate/check-expression.cpp
M flang/test/Semantics/resolve69.f90
M flang/test/Semantics/resolve77.f90
M flang/test/Semantics/spec-expr.f90
Log Message:
-----------
[flang] Accept initialized SAVE local in specification expression (#107656)
Specification expressions may contain references to dummy arguments,
host objects, module variables, and variables in COMMON blocks, since
they will have values on entry to the scope. A local variable with a
initializer and the SAVE attribute (which will always be implied by an
explicit initialization) will also always work, and is accepted by at
least one other compiler, so accept it with a warning.
Commit: cd92c4255582299b9a55fa0dc485982b8f54c49a
https://github.com/llvm/llvm-project/commit/cd92c4255582299b9a55fa0dc485982b8f54c49a
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/runtime/format-implementation.h
Log Message:
-----------
[flang][runtime] Don't emit runtime error for "AA" editing (#107714)
Commas are optional between edit descriptors in a format, so treat "AA"
as if it were "A,A".
Commit: ea858e39bf5b1d09021d142f0c82ef1d4a82d367
https://github.com/llvm/llvm-project/commit/ea858e39bf5b1d09021d142f0c82ef1d4a82d367
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/runtime/io-stmt.h
Log Message:
-----------
[flang][runtime] Accept '\n' as space in internal list-directed input (#107716)
When scanning ahead for the first character in the next input item in
list-directed internal input, allow a newline character to appear and
treat it as a space, matching the behavior of nearly all other Fortran
compilers.
Commit: 15106c26662a573df31e8dfdd9350c313b8bfd84
https://github.com/llvm/llvm-project/commit/15106c26662a573df31e8dfdd9350c313b8bfd84
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/lib/Semantics/expression.cpp
M flang/lib/Semantics/runtime-type-info.cpp
M flang/module/__fortran_type_info.f90
M flang/runtime/assign.cpp
M flang/runtime/descriptor-io.h
M flang/runtime/namelist.cpp
M flang/runtime/type-info.cpp
M flang/runtime/type-info.h
M flang/test/Semantics/typeinfo01.f90
M flang/test/Semantics/typeinfo02.f90
M flang/test/Semantics/typeinfo04.f90
A flang/test/Semantics/typeinfo12.f90
Log Message:
-----------
[flang][runtime] Fix odd "invalid descriptor" runtime crash (#107785)
A defined assignment generic interface for a given LHS/RHS type & rank
combination may have a specific procedure with LHS dummy argument that
is neither allocatable nor pointer, or specific procedure(s) whose LHS
dummy arguments are allocatable or pointer. It is possible to have two
specific procedures if one's LHS dummy argument is allocatable and the
other's is pointer.
However, the runtime doesn't work with LHS dummy arguments that are
allocatable, and will crash with a mysterious "invalid descriptor" error
message.
Extend the list of special bindings to include
ScalarAllocatableAssignment and ScalarPointerAssignment, use them when
appropriate in the runtime type information tables, and handle them in
Assign() in the runtime support library.
Commit: 37f94cd99a5bc4b186651d6967d8595c4786d8ed
https://github.com/llvm/llvm-project/commit/37f94cd99a5bc4b186651d6967d8595c4786d8ed
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/lib/Evaluate/intrinsics.cpp
A flang/test/Evaluate/fold-assumed-rank-kind.f90
Log Message:
-----------
[flang] Accept KIND(x) when x is assumed-rank (#107787)
Don't emit a bogus error about being unable to forward an assumed-rank
dummy argument as an actual argument in the case of the KIND intrinsic
function.
Fixes https://github.com/llvm/llvm-project/issues/107782.
Commit: d418a03e01e6a31b51b0c9dd42ba46da6c47f89d
https://github.com/llvm/llvm-project/commit/d418a03e01e6a31b51b0c9dd42ba46da6c47f89d
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/include/flang/Semantics/scope.h
M flang/lib/Semantics/compute-offsets.cpp
M flang/lib/Semantics/expression.cpp
M flang/lib/Semantics/resolve-names.cpp
M flang/lib/Semantics/symbol.cpp
A flang/test/Semantics/generic10.f90
Log Message:
-----------
[flang] Fix error from semantics on use associated procedure pointer (#107928)
Use associated procedure pointers were eliciting bogus errors from
semantics if their modules also contained generic procedure interfaces
of the same name. (The compiler handles this case correctly when the
specific procedure of the same name is not a pointer.)
With this fix, the test case in
https://github.com/llvm/llvm-project/issues/107784
no longer experiences semantic errors; however, it now crashes
unexpectedly in lowering.
Commit: 5a2071b184e00f086f5b538f2209bcdb8aba3078
https://github.com/llvm/llvm-project/commit/5a2071b184e00f086f5b538f2209bcdb8aba3078
Author: Chris Apple <cja-private at pm.me>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M compiler-rt/lib/rtsan/rtsan_context.cpp
M compiler-rt/lib/rtsan/tests/rtsan_test_utilities.h
M compiler-rt/test/rtsan/basic.cpp
M compiler-rt/test/rtsan/disabler.cpp
Log Message:
-----------
[compiler-rt][rtsan] Improve error message wording to match ASan style (#107620)
Commit: 5495c36104103c4172808a28e8b2df3c806b1d85
https://github.com/llvm/llvm-project/commit/5495c36104103c4172808a28e8b2df3c806b1d85
Author: Heejin Ahn <aheejin at gmail.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/lib/Target/WebAssembly/AsmParser/WebAssemblyAsmTypeCheck.cpp
M llvm/lib/Target/WebAssembly/AsmParser/WebAssemblyAsmTypeCheck.h
Log Message:
-----------
[WebAssembly] Misc. refactoring in AsmTypeCheck (NFC) (#107978)
Existing methods in AsmTypeCheck assumes symbol operand is the 0th
operand; they take a `MCInst` and take `getOperand(0)` on it. I think
passing a `MCOperand` removes this assumption and also is more
intuitive. This was motivated by a new `try_table` instruction, whose
support is going to be added to AsmTypeCheck soon, which has tag symbol
operands in any position, depending on the number and the kinds of catch
clauses. This PR changes all methods' signature that assumes the 0th
operand is the relevant one, even if it's not the symbol operand.
This also adds `getSignature` method, which factors out the common task
when getting a `WasmSignature` from a `MCOperand`.
Commit: ace6d5f2ce53ae88205fc39dafa45e5682fd9a52
https://github.com/llvm/llvm-project/commit/ace6d5f2ce53ae88205fc39dafa45e5682fd9a52
Author: Jorge Gorbe Moya <jgorbe at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/include/llvm/SandboxIR/SandboxIR.h
M llvm/lib/SandboxIR/SandboxIR.cpp
Log Message:
-----------
[SandboxIR] Fix base class of FenceInst. Verify instructions when building a BB in debug mode. (#108078)
@vporpo suggested in an offline conversation that verifying all
instructions during `BasicBlock::buildBasicBlockFromLLVMIR` would be a
good way to get coverage for errors like this during testing. He also
suggested not gating it on `SBVEC_EXPENSIVE_CHECKS` for now as the
checks are pretty basic at the moment and they only affect Debug builds.
Commit: 0fc4147c6d0c5bfb1fd9ed2a9f1c3a70e9281813
https://github.com/llvm/llvm-project/commit/0fc4147c6d0c5bfb1fd9ed2a9f1c3a70e9281813
Author: Philip Reames <preames at rivosinc.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/test/CodeGen/RISCV/rv64zba.ll
Log Message:
-----------
[RISCV] Add test coverage for mul X, C where C=2^N*(3,5,9)*(3,5,9)
Commit: 2ddf21bc702de25a34bb4a13b3610d8cc6bf3ca0
https://github.com/llvm/llvm-project/commit/2ddf21bc702de25a34bb4a13b3610d8cc6bf3ca0
Author: vporpo <vporpodas at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/include/llvm/SandboxIR/PassManager.h
M llvm/lib/SandboxIR/Pass.cpp
M llvm/lib/SandboxIR/PassManager.cpp
M llvm/unittests/SandboxIR/PassTest.cpp
Log Message:
-----------
[SandboxIR] Pass registry (#108084)
This patch implements a simple Pass Registry class, which takes
ownership of the passes registered with it and provides an interface to
get the pass pointer by its name.
Commit: d452429821d3263a73b27387324bc272b47ed1bf
https://github.com/llvm/llvm-project/commit/d452429821d3263a73b27387324bc272b47ed1bf
Author: Peter Klausler <pklausler at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/lib/Evaluate/check-expression.cpp
Log Message:
-----------
[flang] Fix shared library flang build (#108101)
I broke the shared library builds a few minutes ago by introducing a
cyclic dependency between two parts of the compiler. Fix.
Commit: 957af7373881e62eec34ca87106fa2a2c2391d8e
https://github.com/llvm/llvm-project/commit/957af7373881e62eec34ca87106fa2a2c2391d8e
Author: Vitaly Buka <vitalybuka at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M compiler-rt/lib/sanitizer_common/sanitizer_tls_get_addr.cpp
Log Message:
-----------
[sanitizer] Add CHECKs to validate calculated TLS range (#107941)
Commit: 10c04d9873dbbbca26f4d996396da297b9144add
https://github.com/llvm/llvm-project/commit/10c04d9873dbbbca26f4d996396da297b9144add
Author: Jacob Lalonde <jalalonde at fb.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M lldb/test/API/commands/statistics/basic/TestStats.py
Log Message:
-----------
[LLDB]Skip Summary Statistics Tests for Windows (#108079)
Follow up to #102708, the tests are failing for windows. There is a
large variance in these tests between summary strings and built in
types. I'm disabling these test for windows, and will add windows
specific tests as a follow up to this.
Commit: 6007ad79afeffb1288781b4a7241290386293aff
https://github.com/llvm/llvm-project/commit/6007ad79afeffb1288781b4a7241290386293aff
Author: Henrik G. Olsson <hnrklssn at gmail.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/utils/lit/lit/TestRunner.py
R llvm/utils/lit/tests/Inputs/escape-color/color-escaped.txt
R llvm/utils/lit/tests/Inputs/escape-color/color.txt
R llvm/utils/lit/tests/Inputs/escape-color/lit.cfg
R llvm/utils/lit/tests/escape-color.py
Log Message:
-----------
Revert "[llvm-lit] Process ANSI color codes in test output when formatting" (#108104)
Reverts llvm/llvm-project#106776 because of a test failure on Windows.
Commit: d14a600b1eb650f05fcd56a7b790e30f1f52e751
https://github.com/llvm/llvm-project/commit/d14a600b1eb650f05fcd56a7b790e30f1f52e751
Author: vporpo <vporpodas at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/include/llvm/SandboxIR/SandboxIR.h
M llvm/include/llvm/SandboxIR/SandboxIRValues.def
M llvm/lib/SandboxIR/SandboxIR.cpp
M llvm/unittests/SandboxIR/SandboxIRTest.cpp
Log Message:
-----------
[SandboxIR] Implement BlockAddress (#107940)
This patch implements sandboxir::BlockAddress mirroring
llvm:BlockAddress.
Commit: bb7286515c0b285382f370232f97ffa7cfcbc550
https://github.com/llvm/llvm-project/commit/bb7286515c0b285382f370232f97ffa7cfcbc550
Author: Sterling-Augustine <56981066+Sterling-Augustine at users.noreply.github.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/include/llvm/SandboxIR/Type.h
M llvm/lib/SandboxIR/Type.cpp
M llvm/unittests/SandboxIR/TypesTest.cpp
Log Message:
-----------
[SandboxIR] Implement FixedVectorType (#107930)
Commit: 5804193e38680683b370cb3ced46c018d4dbd1b2
https://github.com/llvm/llvm-project/commit/5804193e38680683b370cb3ced46c018d4dbd1b2
Author: Florian Mayer <fmayer at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M compiler-rt/lib/sanitizer_common/sanitizer_tls_get_addr.cpp
Log Message:
-----------
Revert "[sanitizer] Add CHECKs to validate calculated TLS range" (#108112)
Reverts llvm/llvm-project#107941
Broke PPC bot
Commit: 829ea59ddaf0ddfa1d9316a9260bd3ba17562ffe
https://github.com/llvm/llvm-project/commit/829ea59ddaf0ddfa1d9316a9260bd3ba17562ffe
Author: Reid Kleckner <rnk at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/docs/DeveloperPolicy.rst
M llvm/docs/FAQ.rst
Log Message:
-----------
[docs] Add a section on AI-generated content to the developer policy (#91014)
Governments around the world are starting to require labelling for
AI-generated content, and some LLVM stakeholders have asked if LLVM
contains AI-generated content. Defining a policy on the use of AI tools
allows us to answer that question affirmatively, one way of the other.
The policy proposed here allows the use of AI tools in LLVM
contributions, flowing from the idea that any contribution is fine
regardless of how it is made, as long as the contributor has the right
to license it under the project license.
I gathered input from the community in this RFC and incorporated it into the policy:
https://discourse.llvm.org/t/rfc-define-policy-on-ai-tool-usage-in-contributions/78758
Commit: ae5f1a78d3a930466f927989faac8e0b9d820a7b
https://github.com/llvm/llvm-project/commit/ae5f1a78d3a930466f927989faac8e0b9d820a7b
Author: Teresa Johnson <tejohnson at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/lib/Transforms/IPO/MemProfContextDisambiguation.cpp
Log Message:
-----------
[MemProf] Convert CallContextInfo to a struct (NFC) (#108086)
As suggested in #107918, improve readability by converting this tuple to
a struct.
Commit: d2f25e5405cce348913994db71a5efb0c1cf7f28
https://github.com/llvm/llvm-project/commit/d2f25e5405cce348913994db71a5efb0c1cf7f28
Author: Craig Topper <craig.topper at sifive.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M llvm/lib/CodeGen/SelectionDAG/LegalizeIntegerTypes.cpp
M llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/lanai_isel.ll.expected
Log Message:
-----------
[LegalizeTypes] Avoid creating an unused node in ExpandIntRes_ADDSUB. NFC
The Hi result is sometimes calculated a different way and this
node goes unused. Defer creation until we know for sure it is neeeded.
The test changes is because the node creation order changed the names
in the debug output.
Commit: db7e8f2ae81fe10170dc202e45ee8b784e75c74c
https://github.com/llvm/llvm-project/commit/db7e8f2ae81fe10170dc202e45ee8b784e75c74c
Author: Arthur Eubanks <aeubanks at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M compiler-rt/lib/sanitizer_common/sanitizer_internal_defs.h
Log Message:
-----------
[compiler-rt] Hardcode uptr/sptr typedefs on Linux Arm (#108105)
After #106155, Android arm32 asan builds stopped working with missing
definition linker errors. This is due to inconsistent definitions of
`uptr` of either `unsigned long` or `unsigned int` even between TUs in
compiler-rt. This is caused by Linux arm32 headers redefining
`__UINTPTR_TYPE__` (see `arch/arm/include/uapi/asm/types.h` in the Linux
kernel repo), meaning include order/whether or not the Linux header is
included changes compiler-rt symbol mangling.
As a workaround, this hardcodes `uptr`/`sptr` in compiler-rt to
`unsigned int`/`int` on Linux arm32, matching clang/gcc.
Commit: 43f06380cc146518e55d4ebaa369be0909a1f529
https://github.com/llvm/llvm-project/commit/43f06380cc146518e55d4ebaa369be0909a1f529
Author: Florian Mayer <fmayer at google.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M compiler-rt/lib/rtsan/rtsan_context.cpp
M compiler-rt/lib/rtsan/tests/rtsan_test_utilities.h
M compiler-rt/lib/sanitizer_common/sanitizer_internal_defs.h
M compiler-rt/test/rtsan/basic.cpp
M compiler-rt/test/rtsan/disabler.cpp
M flang/docs/Extensions.md
M flang/include/flang/Common/Fortran-features.h
M flang/include/flang/Evaluate/expression.h
M flang/include/flang/Evaluate/tools.h
M flang/include/flang/Semantics/scope.h
M flang/include/flang/Semantics/type.h
M flang/lib/Evaluate/check-expression.cpp
M flang/lib/Evaluate/expression.cpp
M flang/lib/Evaluate/fold-implementation.h
M flang/lib/Evaluate/intrinsics.cpp
M flang/lib/Evaluate/type.cpp
M flang/lib/Semantics/check-declarations.cpp
M flang/lib/Semantics/compute-offsets.cpp
M flang/lib/Semantics/expression.cpp
M flang/lib/Semantics/resolve-names.cpp
M flang/lib/Semantics/runtime-type-info.cpp
M flang/lib/Semantics/symbol.cpp
M flang/lib/Semantics/type.cpp
M flang/module/__fortran_type_info.f90
M flang/runtime/assign.cpp
M flang/runtime/descriptor-io.h
M flang/runtime/format-implementation.h
M flang/runtime/io-stmt.h
M flang/runtime/namelist.cpp
M flang/runtime/time-intrinsic.cpp
M flang/runtime/type-info.cpp
M flang/runtime/type-info.h
A flang/test/Evaluate/fold-assumed-rank-kind.f90
A flang/test/Semantics/Inputs/modfile66.cuf
A flang/test/Semantics/Inputs/modfile67.mod
A flang/test/Semantics/generic10.f90
A flang/test/Semantics/modfile66.f90
A flang/test/Semantics/modfile67.f90
M flang/test/Semantics/resolve24.f90
M flang/test/Semantics/resolve69.f90
M flang/test/Semantics/resolve77.f90
M flang/test/Semantics/spec-expr.f90
M flang/test/Semantics/typeinfo01.f90
M flang/test/Semantics/typeinfo02.f90
M flang/test/Semantics/typeinfo04.f90
A flang/test/Semantics/typeinfo12.f90
M libcxx/include/string
M lldb/test/API/commands/statistics/basic/TestStats.py
M llvm/docs/DeveloperPolicy.rst
M llvm/docs/FAQ.rst
M llvm/include/llvm/SandboxIR/PassManager.h
M llvm/include/llvm/SandboxIR/SandboxIR.h
M llvm/include/llvm/SandboxIR/SandboxIRValues.def
M llvm/include/llvm/SandboxIR/Type.h
M llvm/lib/CodeGen/SelectionDAG/LegalizeIntegerTypes.cpp
M llvm/lib/SandboxIR/Pass.cpp
M llvm/lib/SandboxIR/PassManager.cpp
M llvm/lib/SandboxIR/SandboxIR.cpp
M llvm/lib/SandboxIR/Type.cpp
M llvm/lib/Target/WebAssembly/AsmParser/WebAssemblyAsmTypeCheck.cpp
M llvm/lib/Target/WebAssembly/AsmParser/WebAssemblyAsmTypeCheck.h
M llvm/lib/Transforms/IPO/MemProfContextDisambiguation.cpp
M llvm/test/CodeGen/RISCV/rv64zba.ll
M llvm/test/tools/UpdateTestChecks/update_llc_test_checks/Inputs/lanai_isel.ll.expected
M llvm/unittests/SandboxIR/PassTest.cpp
M llvm/unittests/SandboxIR/SandboxIRTest.cpp
M llvm/unittests/SandboxIR/TypesTest.cpp
M llvm/utils/lit/lit/TestRunner.py
R llvm/utils/lit/tests/Inputs/escape-color/color-escaped.txt
R llvm/utils/lit/tests/Inputs/escape-color/color.txt
R llvm/utils/lit/tests/Inputs/escape-color/lit.cfg
R llvm/utils/lit/tests/escape-color.py
Log Message:
-----------
rebase
Created using spr 1.3.4
Compare: https://github.com/llvm/llvm-project/compare/1d782d013bb9...43f06380cc14
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list