search for: unsplittable

...h (the unsplitable blocks for instance) got addressed, but > I'm having trouble tracking all the changes in discussion. Even just a > quick list of "and we changed X" would be helpful. > We should do an updated summary, but I've been busy. We really do need to keep the unsplittable catchblocks, though. Fundamentally, what we have is control flow described by data. This proposal essentially adds LLVM instructions that model that data. We can't insert real instructions like loads and stores between EH dispatch table entries, so it's forbidden. We can compensate for all...

One of my friends wondered how legal is it to use native comctl32.dll in wine? He owns a license, and he called to MS support, and they told him that Windows is unsplittable piece of software, so comctl32.dll cannot be used separately. So, what's the deal?

...tance) got addressed, but > I'm having trouble tracking all the changes in discussion. Even just a > quick list of "and we changed X" would be helpful. > > > > We should do an updated summary, but I've been busy. > > > > We really do need to keep the unsplittable catchblocks, though. > Fundamentally, what we have is control flow described by data. This > proposal essentially adds LLVM instructions that model that data. We can't > insert real instructions like loads and stores between EH dispatch table > entries, so it's forbidden. > &...

...ck in the CFG that can't have > instructions added to it) that any code placement algorithms (PRE, PGO > probe insertion, Phi elimination, RA spill/copy placement, etc.) may need > to be adjusted for. The adjustments aren't terrible (conceptually it's no > worse than having unsplittable edges from each of the block's preds to each > of its succs), but it's something to be aware of. > No, LLVM doesn't have anything like this yet. It does have unsplittable critical edges, which can come from indirectbr and the unwind edge of an invoke. I don't think it'll...

...#################################################### # The 'evaluation' function. Called once per node. # Produce a label (1 or more elements long) for labeling each node, # and a deviance. The latter is # - of length 1 # - equal to 0 if the node is "pure" in some sense (unsplittable) # - does not need to be a deviance: any measure that gets larger # as the node is less acceptable is fine. # - the measure underlies cost-complexity pruning, however temp1 <- function(y, wt, parms) { print("***** START: TEMP1 *****"); n <- length(y);...

...y split a load or a store. More importantly, we likely would not > wish to split a load or a store as the point of SROA is to make SSA-able > values. Thus what we really want to do is build a partitioning that > attempts to assign a disjoint partition to each collection of overlapping > unsplittable uses. The splittable uses will then be split as necessary to > satisfy this partitioning. > > The result is a pass which can handle arbitrarily large arrays and > structures and split single value loads and stores out of these large > allocas by splitting up any large memcpy or memse...

> optimizing EH codepaths is not usually performance critical. >> Leaving aside the rest of the thread, I feel the need to refute this point in isolation. I've found that optimizing (usually simplifying and eliminating) exception paths ends up being *extremely* important for my workloads. Failing to optimize exception paths sufficiently tends to indirectly hurt things like inlining

After a long tale of sorrow and woe, my colleagues and I stand here before you defeated. The Itanium EH representation is not amenable to implementing MSVC-compatible exceptions. We need a new representation that preserves information about how try-catch blocks are nested. WinEH background ------------------------------- Skip this if you already know a lot about Windows exceptions. On Windows,

For anyone following along on ToT using the gc.statepoint mechanism, you should know that ToT is currently not able to express arbitrary exceptional control flow and relocations along exceptional edges. This is a direct result of moving the gc.statepoint representation to using a token type landingpad. Essentially, we have a design inconsistency where we expect to be able to