mvc: PortField: "wins" is known as "nameserver", sort list #9835
It makes sense to test all of these values in the unittest then
before this breaks during an OS update.
[NFC] Re-enable MSVC C4611 diagnostic (#182100)
From MSDN:
https://learn.microsoft.com/en-us/cpp/error-messages/compiler-warnings/compiler-warning-level-4-c4611?view=msvc-170
I do not believe this diagnostic happens in our code base any longer.
This diagnostic was disabled in 5c73e1f85c5d37a5b037c70f3c112eec5646acb3
and the review for it (https://reviews.llvm.org/D8572) says there were
two instances of the diagnostic as of 2015. But because this is about
interaction between `setjmp` and C++ object destruction, I don't think
we need to disable this diagnostic across the entire monorepo; we can
silence it for the project using setjmp if it still exists.
I enabled the diagnostic locally and my build was warning-free but I'd
like to see how pre- (and post-)commit CI do with this one.
Revert "[ValueTracking] Fix crash in PR175590" (#182478)
Reverts llvm/llvm-project#180355
It caused assert failures:
```
llvm/include/llvm/IR/InstrTypes.h:2351:
Value *llvm::CallBase::getOperand(unsigned int) const:
Assertion `i_nocapture < OperandTraits<CallBase>::operands(this) &&
"getOperand() out of range!"' failed.
```
See comment on the PR for a reproducer.
Remove LEGACY_SHARE validation for path_suffix
Prior to 25.10 we did not validate what users were putting as
a path_suffix in SMB shares that supported them. When the new
schema was added, a common path suffix type was used to limit
users to what makes sense (excluding options that were
directly under the client's control since they can lead to
the incorrect understanding that shares are isolated from
each other in a way that enhances device security.
This commit removes the path suffix validation from the
LEGACY_SHARE purpose, but keeps it for other ones.
[llvm-pdbutil] Dump and parse unknown records (#180761)
When new record types or leaf kinds are added to CodeView, then we
should try to dump all the information we have on these records.
- If a type or symbol is unknown, the raw data is now always shown.
Before, you'd have to set `--sym-data` or `--type-data` (but that would
show it for all types).
- Converting to/from YAML, unknown records are now included. Before we'd
error out.
I stumbled upon this when checking PDBs from C++ 20 coroutines compiled
with MSVC. These contain the symbol records `0x1171` and `0x117c`, which
we don't handle yet.
[CMake][LLVM] Add PCH infrastructure and LLVMSupport PCH (#176420)
This patch implements PCH support. PCH is enabled by default, unless
noted below, and can be disabled with
-DCMAKE_DISABLE_PRECOMPILE_HEADERS=ON.
* Libraries can define precompiled headers using a newly added
PRECOMPILE_HEADERS keyword. If specified, the listed headers will be
compiled into a pre-compiled header using standard CMake mechanisms.
* Libraries that don't define their own PRECOMPILE_HEADERS but directly
depend on a library or component that defines its own PCH will reuse
that PCH. This reuse is not transitive to prevent excessive use of
unrelated headers. If multiple dependencies provide a reusable PCH, the
first one with the longest dependency chain (stored in the CMake target
property LLVM_PCH_PRIORITY) is used. However, due to CMake limitations,
only PCH from targets that are already defined can be reused; therefore
libraries that should reuse a PCH must be defined later in the CMake
file (=> add_subdirectory order matters).
[34 lines not shown]
AMDGPU/GlobalISel: Regbanklegalize rules for INTRIN_IMAGE
Regbanklegalize rules for INTRIN_IMAGE loads and stores.
Because of very large number of different type signatures, rule specifies
only function for lowering (waterfall lowering of RsrcIdx operand if needed)
and this function also applies register banks.
[NFC][SPIRV] Replace uses of `removeFromParent` by `eraseFromParent` (#182330)
`removeFromParent` doesn't deallocate the resources associated with the
`MachineInstruction`.
I was not able to remove all the uses of `removeFromParent` in the file;
but these are the safe ones.
There is an extra advantage with `eraseFromParent`: If we reuse the
deleted instruction the address sanitizer will catch the mistake.
www/access-log-exporter: Add new port
access-log-exporter is a Prometheus exporter that receives web server
access logs via syslog and converts them into metrics.
access-log-exporter processes logs from multiple web servers and has
undergone testing with Nginx and Apache HTTP Server 2.4. It supports
flexible metric configuration through presets and provides comprehensive
monitoring capabilities for web traffic analysis.
firewall: fix running into error using well known protocols with "-" in them #9835
The ordering is debatable. For now just make sure that we didn't miss the
chance to look up the original one and accept it as is.
[analyzer] Remove the alpha.core.FixedAddr checker (#182033)
This checker is way to simplistic. It's also alpha. I don't think it's
worth for anyone keeping it, especially that we have an
`optin.core.FixedAddressDereference` checker that largely supresedes
this alpha checker.
I propose the removal of this checker.
Also relates to:
https://github.com/llvm/llvm-project/pull/181858#discussion_r2818756964
[CIR] Handle Type::OverflowBehavior in CIR CodeGen
Add handling for the newly introduced Type::OverflowBehavior type class
in CIRGenItaniumCXXABI.cpp and CIRGenFunction.cpp switch statements to
fix -Werror,-Wswitch compilation errors.
[InstCombine] Do not perform fcmp -> icmp transformation if denormal inputs may be flushed (#181899)
Commit 4827771234276 added the following transformation:
fcmp oeq/une (bitcast X), 0.0 --> (and X, SignMaskC) ==/!= 0
This transformation is only valid if denormal inputs are preserved. If
they are flushed, the two comparisons can return different results.
---------
Co-authored-by: Justin Holewinski <jholewinski at nvidia.com>
[ASan] Fix test IsPoisonedDoesNotCrashOnMemoryBoundaries for 32-bit targets (#182412)
Make sure there is no address space overflow in the test on 32-bit platforms.
32-bit: __asan_region_is_poisoned(0xffffffff, 1) fails since 0xffffffff + 1 = 0x0
