search for: basic_block

Hello I used a functionPass to count the number of bloks ? so for each BBlock I check if it is a loop or BB ... and I'm wandring How can I determine if a BB is a conditional block (if) ?? and How can I separate between the BBs inside the if and those inside the else ?? Thank you so much K.H -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sep 3, 2010, at 3:20 AM, Jeff Kunkel wrote: > Perhaps what I think is a problem really is not a problem. Yep. > The information I need is where the jumps occurs in the instructions vector. The machine instructions are already separated into basic blocks. http://en.wikipedia.org/wiki/Basic_block /jakob

Perhaps what I think is a problem really is not a problem. So when a jump occurs from one block A to block B, then the registers are certain state, and register allocation happens with the initial state defined by A->B. When a third block C jumps to block B, the state of the registers are different. Thus register allocation needs to account for the jump from C->B, by a few ways: 1. The

...supported as the "storage" parameter? Is it only allocas? I've also had some success with a combination of llvm::Argument and DIBuilder::createComplexVariable(). That is, create a DIVariable with one additional OpDeref and then use DIBuilder::insertDeclare(argument, variable_info, basic_block). Is this kind of usage supported or do I always have to use allocas to make this work reliably? Thanks in advance, Michael

It is at the end allowing for oddities like debug info and multiple branches. You might want to look at AnalyzeBranch. On Sep 2, 2010, at 4:19 PMPDT, Jeff Kunkel wrote: > Is there any way to tell where in the Instruction list, the branch > to the other MachineBasicBlock happens? I know in the BasicBlock had > a nice api for it. > > Thanks, > Jeff Kunkel > > On Thu,

...inction. > > > > I see, you are proposing encoding these profile in the metadata. I > agree that this can work, but from implementation's perspective, it > could could lead to great complexity. > Sample PGO pass first read in the source->count map, use it to get > basic_block->count map, and then use heuristics to propagate and get > branch->probability count. So we don't have Metadata to store the > raw count, but only the branch probability is stored after sample > pgo pass. I think that, as you indicate below, we'd need to change this to {sour...

When looking into https://llvm.org/bugs/show_bug.cgi?id=24866, I discovered that the root cause of the crash is that I was expecting every basic block to have a corresponding Node in the dominator tree. Apparently, the "while.end" basic block in the example does not have a Node in the Dominator Tree. Can anyone tell me if this is expected? If so, under what circumstances?

...> > I > > > agree that this can work, but from implementation's perspective, > > > it > > > could could lead to great complexity. > > > > > > Sample PGO pass first read in the source->count map, use it to > > > get > > > basic_block->count map, and then use heuristics to propagate and > > > get > > > branch->probability count. So we don't have Metadata to store the > > > raw count, but only the branch probability is stored after sample > > > pgo pass. > > > > > I...

----- Original Message ----- > From: "Hal Finkel via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Dehao Chen" <dehao at google.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Xinliang David Li" > <davidxl at google.com> > Sent: Tuesday, November 1, 2016 4:26:17 PM > Subject: Re: [llvm-dev] (RFC) Encoding code

...variable (LLVM/Clang). Gerald Pfeifer (5): msvcrt/tests: Adjust CHECK_TYPE to avoid some two dozen compiler warnings. oleaut32/tests: Remove variable rValid which is not really used from test_VarMod. rsaenh: Simplify store_key_container_permissions. dbghelp: Remove variable basic_block which is not really used from dwarf2_parse_line_numbers. wordpad: Remove variable bottom which is not really used from print. Hans Leidekker (9): server: Map EHOSTUNREACH to STATUS_HOST_UNREACHABLE. msi: Get rid of the goto in MSI_ApplicablePatchW. msi: Add a test for prope...

...re proposing encoding these profile in the metadata. I >>> agree that this can work, but from implementation's perspective, it could >>> could lead to great complexity. >>> >>> Sample PGO pass first read in the source->count map, use it to get >>> basic_block->count map, and then use heuristics to propagate and get >>> branch->probability count. So we don't have Metadata to store the raw >>> count, but only the branch probability is stored after sample pgo pass. >>> >>> I think that, as you indicate below, w...

...r passes that don't care about the distinction. I see, you are proposing encoding these profile in the metadata. I agree that this can work, but from implementation's perspective, it could could lead to great complexity. Sample PGO pass first read in the source->count map, use it to get basic_block->count map, and then use heuristics to propagate and get branch->probability count. So we don't have Metadata to store the raw count, but only the branch probability is stored after sample pgo pass. I think that, as you indicate below, we'd need to change this to {source, disc}->co...