captive portal: fix regression in 369630d, addresses kept bouncing between zones
If there are multiple zones defined, we shouldn't look at the ipfw output
as it has no notion of zones, therefore the ips were flagged for removal
during each iteration. Limit it to pf instead, as was the case before.
While here, we don't have to query the db for this each time, as the
list_session_ips() call filters out deleted clients.
[Support] Use block numbers for LoopInfo BBMap (#103400)
Replace the DenseMap from blocks to their innermost loop a vector
indexed by block numbers, when possible. Supporting number updates is
not trivial as we don't store a list of basic blocks, so this is not
implemented.
NB: I'm generally not happy with the way loops are stored. As I think
that there's room for improvement, I don't want to touch the
representation at this point.
Pull Request: https://github.com/llvm/llvm-project/pull/103400
[Analysis][NFC] Include LoopInfoImpl only in source file (#187459)
There's no need to include the full LoopInfo implementation in every
source file that uses LoopInfo.
Pull Request: https://github.com/llvm/llvm-project/pull/187459
mvc: BaseField: add setValues() for generic use
A small follow-up to make setValues() work like getValues()
including stripping empty values. Works from everywhere now
and adds a few tests in order to make sure it will keep working.
[DebugInfo] Fix segfault in constructSubprogramScopeDIE with null subprogram type (#184299)
Guard against null DISubroutineType when checking for variadic
parameters in `constructSubprogramScopeDIE`. `DISubprograms` may lack a
type field when using LineTablesOnly emission, causing a null pointer
dereference.
Fixes #184003
Co-authored-by: Shivam Kunwar <phyBrackets at users.noreply.github.com>
import py-flor
Flor - An efficient Bloom filter implementation in Python.
a new dependency needed for security/plaso update.
this is revised version to make tests work by sthen@
[MemorySSA] Fix handling of cross-iteration dependencies for calls (#187291)
The clobber walker has to be careful when it comes to translating
locations across phis. If we're translating across a cycle backedge,
we'll end up working with SSA values from two different cycle iterations
-- something that alias analysis by default assumes is not the case.
To protect against this, the upwards def walk was already discarding the
access size from the memory location if the pointer was not loop
invariant. This (mostly) avoids this issue for memory locations.
However, the same issue also exists for calls. In this case, it's not
possible to adjust the call used for AA queries in a similar way.
Instead, we can make use of the cross-iteration alias analysis mode,
which has been added some time ago for these kinds of situations.
The basic change here is that the upwards def walk, when translating
across a phi, will enable the cross-iteration mode for calls.
Unfortunately, quite a few places have to be changed in order to thread
[8 lines not shown]
