search for: handlemoveintobundl

Hi, I have a custom scheduler/bundler running just after coalescing as proposed by the current infrastructure of machine schedulers. Btw, great thanks for this cool stuff ! I'm running into problems when I want to update the LI information of an instruction. I call handleMoveIntoBundle() to make its LI begins from the packet header but the following assertion is raised: "Can't have two defs for the same variable exiting a bundle." in moveExitingFromInto() IIUC, handleMoveIntoBundle collects entering, internal and exiting live ranges from the bundle and group a...

...> > I have a custom scheduler/bundler running just after coalescing as > proposed by the current infrastructure of machine schedulers. Btw, > great thanks for this cool stuff ! > I'm running into problems when I want to update the LI information of > an instruction. I call handleMoveIntoBundle() to make its LI begins > from the packet header but the following assertion is raised: > > "Can't have two defs for the same variable exiting a bundle." in > moveExitingFromInto() > > IIUC, handleMoveIntoBundle collects entering, internal and exiting > live r...

...a custom scheduler/bundler running just after coalescing as > > proposed by the current infrastructure of machine schedulers. Btw, > > great thanks for this cool stuff ! > > I'm running into problems when I want to update the LI information of > > an instruction. I call handleMoveIntoBundle() to make its LI begins > > from the packet header but the following assertion is raised: > > > > "Can't have two defs for the same variable exiting a bundle." in > > moveExitingFromInto() > > > > IIUC, handleMoveIntoBundle collects entering, inter...

...ler/bundler running just after coalescing as >> > proposed by the current infrastructure of machine schedulers. Btw, >> > great thanks for this cool stuff ! >> > I'm running into problems when I want to update the LI information of >> > an instruction. I call handleMoveIntoBundle() to make its LI begins >> > from the packet header but the following assertion is raised: >> > >> > "Can't have two defs for the same variable exiting a bundle." in >> > moveExitingFromInto() >> > >> > IIUC, handleMoveIntoBundle...

...come in handy. Fortunately we currently do > bundling fairly late, so it is not an issue yet. LiveIntervals should work for your bundles by giving each instruction in the bundle the same slot index. Regalloc should do the right thing. There's a proof-of-concept API in LiveIntervalAnalyses, handleMoveIntoBundle(), that you should try to use. As I was saying in my last message, we may want to improve that API as you actually start testing it. -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120511/d37d45f9/att...

Dave, Thank you for your interest. Please see my replies below. Sorry that my terminology is not as crisp as Andy's, but I think you can see what I mean. Sergei -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum. > -----Original Message----- > From: dag at cray.com [mailto:dag at cray.com] > Sent: Friday, May 11, 2012 12:14 PM > To: Sergei Larin > Cc: