search for: immedit

...n program-counter order. So if you have an epilogue in the middle of a function and emit CFI directives saying the registers are back where they were then the unwinder will think that applies to the rest of the function too. To fix that you'd have to emit yet more directives in the basic block immeditately following the epilogue. Most people don't bother with either because you'd only really need it if you expected to have to catch an exception in the epilogue (which is impossible on most platforms). > Also, the > directives are also for debug purpose (.debug_frame), right? I gues...

Hi all, I am writing a custom backend. Doing more testing i notice that for some reason something like: int test(int x) { return x - 1; } is being turned into this IR: ; Function Attrs: nounwind define i32 @test(i32 %n) #0 { entry: %n.addr = alloca i32, align 4 store i32 %n, i32* %n.addr, align 4 %0 = load i32* %n.addr, align 4 %sub = sub nsw i32 %0, 1 ret i32 %sub } But finally in

2018-01-16 18:18 GMT+08:00 Tim Northover <t.p.northover at gmail.com>: > On 15 January 2018 at 12:49, 陳韋任 via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > - CFI directives: > > > > This is for .eh_frame section. Basically all the targets insert CFI > > directives in FrameLowering, but I am not sure exactly when/where I > should > > do

...ca3c7..6839f88 100644 --- a/drm/nouveau/nvkm/subdev/pmu/fuc/kernel.fuc +++ b/drm/nouveau/nvkm/subdev/pmu/fuc/kernel.fuc @@ -252,7 +252,7 @@ ticks_from_ns: /* try not losing precision (multiply then divide) */ imm32($r13, HW_TICKS_PER_US) - call #mulu32_32_64 + call(mulu32_32_64) /* use an immeditate, it's ok because HW_TICKS_PER_US < 16 bits */ div $r12 $r12 1000 @@ -264,7 +264,7 @@ ticks_from_ns: /* let's divide then multiply, too bad for the precision! */ div $r14 $r14 1000 imm32($r13, HW_TICKS_PER_US) - call #mulu32_32_64 + call(mulu32_32_64) /* this cannot overflo...

...f you > have an epilogue in the middle of a function and emit CFI directives > saying the registers are back where they were then the unwinder will > think that applies to the rest of the function too. > > To fix that you'd have to emit yet more directives in the basic block > immeditately following the epilogue. Most people don't bother with > either because you'd only really need it if you expected to have to > catch an exception in the epilogue (which is impossible on most > platforms). ​My test case is: void foo() { throw 0; } void bar() { try {...

https://bugzilla.samba.org/show_bug.cgi?id=2208 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Status|NEW |ASSIGNED Summary|rsync failed at random file |cygwin version of rsync

...f you > have an epilogue in the middle of a function and emit CFI directives > saying the registers are back where they were then the unwinder will > think that applies to the rest of the function too. > > To fix that you'd have to emit yet more directives in the basic block > immeditately following the epilogue. Most people don't bother with > either because you'd only really need it if you expected to have to > catch an exception in the epilogue (which is impossible on most > platforms). > >> Also, the >> directives are also for debug purpose (....

CentOS 5.2 Postfix 2.3.3 (Came Packed with CentOS) Dovecot 1.1.1 Dovecot-Sieve 1.1.5 Did a complete new fresh install. When I send a message to: test at wildpeacockstudios.com, I get two error messages as listed in the /var/log/maillog: (1) (lost connection with mail.tibonline.net[12.179.81.11] while receiving the initial server greeting) (2) status=bounced (local configuration error. Command

this series fixes the PMU on falcons v5 which fixes memory recklocking on kepler2 and would also allow us to enable memory recklocking on maxwell Karol Herbst (4): pmu/fuc: fix imm32 for gk208+ pmu/fuc: replace mov+sethi with imm32 pmu/fuc: use the call macro instead of using the call instruction directly pmu/fuc: use imm32 in ld/st macros

while trying out my pmu_counter patches on a gk208 gpu, I notived that the pmu is pretty much screwed up there. Karol Herbst (4): pmu/fuc: fix imm32 for gk208+ pmu/fuc: replace mov+sethi with imm32 pmu/fuc: call# seems to be broken on gk208 pmu/fuc: movw is somewhat weird on gk208, use mov instead drm/nouveau/nvkm/subdev/pmu/fuc/gf100.fuc3.h | 1598 +++++++++++------------

Re-use the therm-exported fan structure with only two minor modifications: - pwm_freq: u16 -> u32; - add fan_type (toggle or PWM) v2: - Do not memset the table to 0 as it erases the pre-set default values Signed-off-by: Martin Peres <martin.peres at free.fr> --- drm/Kbuild | 1 + drm/core/include/subdev/bios/fan.h | 1 + drm/core/subdev/bios/fan.c | 1