Displaying 4 results from an estimated 4 matches for "bundleranges".
2012 May 25
2
[LLVMdev] handleMoveIntoBundle assertion
...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 all this information into BundleRanges.
Then it collects the same information for the incoming instruction and
add it to the current BundleRanges while updating its live ranges.
I found that entering, internal and exiting live ranges of the packet
are not cleared before collecting the same information for the incoming
instruction. T...
2012 May 29
2
[LLVMdev] [PATCH] handleMoveIntoBundle assertion
...t; >
> > "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 all this information into
> > BundleRanges. Then it collects the same information for the incoming
> > instruction and add it to the current BundleRanges while updating its
> > live ranges.
> > I found that entering, internal and exiting live ranges of the packet
> > are not cleared before collecting the same informa...
2012 May 29
0
[LLVMdev] [PATCH] handleMoveIntoBundle assertion
...ollowing 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 all this information into
> BundleRanges. Then it collects the same information for the incoming
> instruction and add it to the current BundleRanges while updating its
> live ranges.
> I found that entering, internal and exiting live ranges of the packet
> are not cleared before collecting the same information for the
>...
2012 May 29
0
[LLVMdev] [PATCH] handleMoveIntoBundle assertion
...uot;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 all this information into
>> > BundleRanges. Then it collects the same information for the incoming
>> > instruction and add it to the current BundleRanges while updating its
>> > live ranges.
>> > I found that entering, internal and exiting live ranges of the packet
>> > are not cleared before collecting...