search for: 380b

Displaying 8 results from an estimated 8 matches for "380b".

Did you mean: 380
2017 Sep 26
2
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...3 1: valnos 2 In this particular case, I believe that it is the greedy allocator that is creating the multiple components in the %vreg77 live interval. If you look at the attached debug dump file, just after the greedy allocator runs, the segment of %vreg77 from the def at 312B to the use at 380B seems to be separable from the other segments. The reason the above verification failure is not hit at that point seems to be related to the FIXME in the following snippet from ConnectedVNInfoEqClasses::Classify(): // Normal value defined by an instruction. Check for two-addr redef....
2017 Sep 26
0
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...valnos 2 > > In this particular case, I believe that it is the greedy allocator that is creating the multiple components in the %vreg77 live interval. If you look at the attached debug dump file, just after the greedy allocator runs, the segment of %vreg77 from the def at 312B to the use at 380B seems to be separable from the other segments. The reason the above verification failure is not hit at that point seems to be related to the FIXME in the following snippet from ConnectedVNInfoEqClasses::Classify(): That dump seems to be well before greedy runs, isn't it? At a first glance the...
2017 Sep 26
2
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...2 >> >> In this particular case, I believe that it is the greedy allocator that is creating the multiple components in the %vreg77 live interval. If you look at the attached debug dump file, just after the greedy allocator runs, the segment of %vreg77 from the def at 312B to the use at 380B seems to be separable from the other segments. The reason the above verification failure is not hit at that point seems to be related to the FIXME in the following snippet from ConnectedVNInfoEqClasses::Classify(): > That dump seems to be well before greedy runs, isn't it? I'm not sure...
2017 Sep 26
0
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...;> >>> In this particular case, I believe that it is the greedy allocator that is creating the multiple components in the %vreg77 live interval. If you look at the attached debug dump file, just after the greedy allocator runs, the segment of %vreg77 from the def at 312B to the use at 380B seems to be separable from the other segments. The reason the above verification failure is not hit at that point seems to be related to the FIXME in the following snippet from ConnectedVNInfoEqClasses::Classify(): >> That dump seems to be well before greedy runs, isn't it? > > I&...
2017 Sep 27
2
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...eedy allocator >>>> that is creating the multiple components in the %vreg77 live >>>> interval.  If you look at the attached debug dump file, just after >>>> the greedy allocator runs, the segment of %vreg77 from the def at >>>> 312B to the use at 380B seems to be separable from the other >>>> segments.  The reason the above verification failure is not hit at >>>> that point seems to be related to the FIXME in the following snippet >>>> from ConnectedVNInfoEqClasses::Classify(): >>> That dump seems...
2017 Sep 27
0
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...gt;>>>> In this particular case, I believe that it is the greedy allocator that is creating the multiple components in the %vreg77 live interval. If you look at the attached debug dump file, just after the greedy allocator runs, the segment of %vreg77 from the def at 312B to the use at 380B seems to be separable from the other segments. The reason the above verification failure is not hit at that point seems to be related to the FIXME in the following snippet from ConnectedVNInfoEqClasses::Classify(): >>>> That dump seems to be well before greedy runs, isn't it? >&...
2010 Mar 02
3
Very unresponsive, sometimes stalling domU (5.4, x86_64)
...0|8192B 312k| 66B 178B| 0 0 | 81 36 0 0 56 44 0 0| 0 560k| 186B 178B| 0 0 | 103 44 0 0 43 57 0 0| 0 488k| 126B 178B| 0 0 | 91 16 0 0 50 50 0 0| 0 408k| 126B 178B| 0 0 | 59 12 0 0 64 36 0 0| 72k 120k| 380B 566B| 0 0 | 140 87 0 0 44 56 0 0| 0 0 | 66B 178B| 0 0 | 9 10 0 0 55 45 0 0| 16k 0 | 126B 178B| 0 0 | 32 38 2 0 21 78 0 0| 72k 744k| 846B 2038B| 0 0 | 243 275 0 0 44 56 0 0| 0 0 | 186B 178B| 0...
2010 Mar 02
3
Very unresponsive, sometimes stalling domU (5.4, x86_64)
...0|8192B 312k| 66B 178B| 0 0 | 81 36 0 0 56 44 0 0| 0 560k| 186B 178B| 0 0 | 103 44 0 0 43 57 0 0| 0 488k| 126B 178B| 0 0 | 91 16 0 0 50 50 0 0| 0 408k| 126B 178B| 0 0 | 59 12 0 0 64 36 0 0| 72k 120k| 380B 566B| 0 0 | 140 87 0 0 44 56 0 0| 0 0 | 66B 178B| 0 0 | 9 10 0 0 55 45 0 0| 16k 0 | 126B 178B| 0 0 | 32 38 2 0 21 78 0 0| 72k 744k| 846B 2038B| 0 0 | 243 275 0 0 44 56 0 0| 0 0 | 186B 178B| 0...