search for: pesimm

Displaying 8 results from an estimated 8 matches for "pesimm".

Did you mean: pesimo
2009 Nov 15
2
[LLVMdev] Crash in PBQP register allocator
...nd a finite cost solution, even though one exists. The infinite cost solution will always be in violation of some rule of register allocation (failing to handle an interference, or spilling an infinite cost node for instance). There are several ways to fix the issue with the solver, but most would pesimmize allocation quality in the general case. I will look for a better solution when I return to the University of Sydney in a couple of weeks. In the mean time I have added an assert to the allocator to ensure that infinite cost solutions do not produce miscompilations. For programs which trigger the...
2009 Dec 15
2
[LLVMdev] Crash in PBQP register allocator
...nite cost > > solution will always be in violation of some rule of register > > allocation (failing to handle an interference, or spilling an infinite > > cost node for instance). > > > > There are several ways to fix the issue with the solver, but most > > would pesimmize allocation quality in the general case. I will look > > for a better solution when I return to the University of Sydney in a > > couple of weeks. In the mean time I have added an assert to the > > allocator to ensure that infinite cost solutions do not produce > > miscomp...
2009 Nov 17
0
[LLVMdev] Crash in PBQP register allocator
...n though one exists. The infinite cost > solution will always be in violation of some rule of register > allocation (failing to handle an interference, or spilling an infinite > cost node for instance). > > There are several ways to fix the issue with the solver, but most > would pesimmize allocation quality in the general case. I will look > for a better solution when I return to the University of Sydney in a > couple of weeks. In the mean time I have added an assert to the > allocator to ensure that infinite cost solutions do not produce > miscompilations. For progra...
2009 Dec 15
0
[LLVMdev] Crash in PBQP register allocator
...ion will always be in violation of some rule of register > > > allocation (failing to handle an interference, or spilling an infinite > > > cost node for instance). > > > > > > There are several ways to fix the issue with the solver, but most > > > would pesimmize allocation quality in the general case. I will look > > > for a better solution when I return to the University of Sydney in a > > > couple of weeks. In the mean time I have added an assert to the > > > allocator to ensure that infinite cost solutions do not produce &g...
2010 Jan 26
3
[LLVMdev] Crash in PBQP register allocator
...n violation of some rule of register >> > > allocation (failing to handle an interference, or spilling an infinite >> > > cost node for instance). >> > > >> > > There are several ways to fix the issue with the solver, but most >> > > would pesimmize allocation quality in the general case. I will look >> > > for a better solution when I return to the University of Sydney in a >> > > couple of weeks. In the mean time I have added an assert to the >> > > allocator to ensure that infinite cost solutions do no...
2009 Nov 13
0
[LLVMdev] Crash in PBQP register allocator
This looks like a bug in the PBQP solver. I'm currently investigating. Cheers, Lang. On Thu, Nov 12, 2009 at 12:46 AM, <Sachin.Punyani at microchip.com> wrote: > Hi, > > > > Please see the two “.ll’ files attached. > > > > Command line used > > llc –march=pic16  –pre-RA-sched=list-burr –regalloc=pbqp new.obc > > > > The above test case
2009 Nov 12
2
[LLVMdev] Crash in PBQP register allocator
Hi, Please see the two ".ll' files attached. Command line used llc -march=pic16 -pre-RA-sched=list-burr -regalloc=pbqp new.obc The above test case crashes only when I use the combination of list-burr scheduler and pbqp register allocator. If any of them (scheduler or register allocator) is replaced with some alternate then I don't see the crash. I could not figure
2010 Jan 28
0
[LLVMdev] Crash in PBQP register allocator
...n of some rule of register >>>>> allocation (failing to handle an interference, or spilling an infinite >>>>> cost node for instance). >>>>> >>>>> There are several ways to fix the issue with the solver, but most >>>>> would pesimmize allocation quality in the general case. I will look >>>>> for a better solution when I return to the University of Sydney in a >>>>> couple of weeks. In the mean time I have added an assert to the >>>>> allocator to ensure that infinite cost solutions...