[clang][Modules] Handle relocated modules during implicit module builds (#181836)
* To avoid the build time overhead of checking for relocated modules,
only check it once per build session.
* Enable relocated module checks in the dependency scanner.
* Add remarks to know when this is happening with `-Rmodule-validation`
This check is necessary to be able to handle new libraries appearing in
earlier search paths. This is a valid scenario when dependency info
changes between incremental builds of the same scheme, thus new build
sessions.
It is still malformed to expect new versions of libraries to be added
within the same build session.
resolves: rdar://169174750
math/octave-forge-apa: New port.
Arbitrary Precision Arithmetic (APA) package for Octave/Matlab. This
package is a wrapper around the MPFR library, which provides arbitrary
precision floating-point arithmetic. The package allows users to perform
calculations with a precision that can be set at runtime, making it
suitable for applications that require high precision, such as numerical
analysis and scientific computing.
[APINotes] Refactor APINotesReader to propagate llvm::Error (#183812)
**Context:** While exploring the `APINotes` codebase, I found 54 `FIXME`
comments in `APINotesReader.cpp` stating: `// FIXME this drops the error
on the floor.`
This happened because the internal `read*Block` methods returned a
boolean, and the `APINotesReader` constructor reported failures via a
`bool &Failed` out-parameter. This forced the actual `llvm::Errors`
returned from the bitstream cursor to be silently consumed with
`consumeError()`.
This patch refactors this behavior to properly propagate the errors up
the stack.
**Changes in this patch:**
**1.** Changed all `read*Block` methods in
`APINotesReader::Implementation` to return `llvm::Error` instead of
[12 lines not shown]
[flang][OpenMP] Support custom mappers in target update to/from clauses (#169673)
Implement support for the OpenMP `mapper` modifier on `target update` `to` and
`from` clauses in Flang.
Semantic name resolution is extended to bind the mapper symbol for
`OmpClause::To` and `OmpClause::From` via a shared `ResolveMapperModifier`
helper. Lowering is extended in `ClauseProcessor` with a `getMapperIdentifier`
template helper to extract the mapper name for both `map` and `target update`
clauses and forward it to `omp.map_info`.
Fixes #168701.
Reviewed By: TIFitis, kparzysz
Assited By: Copilot( For review and articulations of messages)
opentofu16: Import opentofu16-1.6.2
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
* Infrastructure as Code: Infrastructure is described using a
high-level configuration syntax. This allows a blueprint of your
datacenter to be versioned and treated as you would any other code.
Additionally, infrastructure can be shared and re-used.
* Execution Plans: OpenTofu has a "planning" step where it generates
an execution plan. The execution plan shows what OpenTofu will do
when you call apply. This lets you avoid any surprises when
OpenTofu manipulates infrastructure.
* Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
[7 lines not shown]
[SystemZ][z/OS] Remove use of subsections.
HLASM has no notion of subsections. There are several possible solutions
how to deal with this. However,
- using a different section introduces a lot of relocations, which slows
down the binder later
- emitting the PPA1 after the code changes the location which may break
existing tools
The choosen solution is to record the PPA1 data, and emit them at the
end of the assembly into the code section. This solves both issues,
at the expense of having to do some bookkeeping.
This change moves the position of the PPA2, too, but this is less
critical.
[clang][ssaf] Add `JSONFormat` serialization support for `LUSummary` and `LUSummaryEncoding`
This change extends `SerializationFormat` and `JSONFormat` with APIs to
read and write `LUSummary` and `LUSummaryEncoding`, completing the
serialization interface for both TU-level and LU-level summaries. As
part of the implementation, common serialization infrastructure has been
extracted into `JSONFormatImpl.{cpp, h}`, eliminating duplication across
the TU and LU translation units. A comprehensive `LUSummaryTest` suite
has been added to test `LUSummary` and `LUSummaryEncoding`, mirroring
the structure of the existing `TUSummaryTest` suite. Shared testing
infrastructure has been extracted into `JSONFormatTest.{cpp, h}`.
[mlir][bazel] Fix build after moving AMX into X86 in #183717. (#184165)
This PR fixes the bazel build that got broken by #183717, which moved
the AMX dialect into the X86 dialect. The fix consists of replicating
the changes from the CMake files into BUILD files as usual; in this
case, mostly removing the AMX dialect targets, adding a few new
references to the corresponding X86 targets, and adding a few new
dependencies to the existing X86 targets due to the new code.
Signed-off-by: Ingo Müller <ingomueller at google.com>
[LinkerWrapper] Fix a bunch of minor issues and typos (#183679)
Summary:
A bunch of small issues found through linting and LLM checking.
- Broken sort comparator that violated strict weak ordering (UB)
- SearchLibrary corrupting .lib filenames via erroneous drop_front()
- Hardcoded x86_64-unknown-linux-gnu host triple in AMDGPU fatbinary
- OffloadFile loop variable shadowing its own type, causing std::move on
the type rather than the variable
- GetDeviceInput calling exit() directly instead of returning Error
- Redundant double-wrapping of DerivedArgList
- Various typo and style fixes
Firewall: Rules [new]: adjust row selection behavior for internal rules
re-use the same logic that decides checkbox rendering to disable the
relevant hover CSS and disable tabulator internal selection functionality
(cherry picked from commit 4bc542cc7fad2ccd11e08bcd7bd2266f2accefd1)
Stop the canonicalization of the path in pledge_namei() callback since
we know is providing strictly normalized paths, and it leads to a subtle
problem a little bit like a TOCTOU. However, this pathcode can also be
reached by non-libc callers, so we need one validation step: the zoneinfo
sub-directory inspections may not attempt walks upwards through "..", we
don't need to consider symbolic links because root does not place them there.
From discussions with david leadbeater, ok beck
security/sshpass: Update to 1.10
Changelog:
Version 1.10
* Convert repo to git
* Remove sig unsafe functions from signal handler (Ticket #22).
* Allow -e to explicitly specify the environment variable to use
(Ticket #5).
* Unset the variable specified with -e before calling subprogram
(Ticket #25).
* Change the logic for setting a controlling TTY. Fixes compatibility
issues with OpenSolaris and MSYS/Cygwin. Thanks Marcin Olszewski for
the fix.
Version 1.09
* Explicitly set the controlling TTY (SF patch #7)
Version 1.08
* Report when IP key has changed (Closes Debian bug #730101)
[7 lines not shown]
[X86] known-never-zero.ll - add additional demanded elts vector test coverage (#184159)
vector variants of existing tests where we only demand 1 element for the
never zero test
