search for: pass6

...2014 at 10:39 PM, Keno Fischer <kfischer at college.harvard.edu> wrote: > I don't think we're doing anything unusual. Here's the relevant snippet from > the generated IR for ccall (after instrumentation): > > ccall: ; preds = %pass6, %113 > %114 = phi i8* [ %110, %113 ], [ %108, %pass6 ] > %115 = inttoptr i64 %17 to i64* > %116 = bitcast i8* %69 to i32*, !dbg !7 > %117 = bitcast i8* %114 to i32 (i32*, i64, i64)*, !dbg !7 > store i64 %_msret13, i64* getelementptr inbounds ([1000 x i64]* > @__msan_par...

...t college.harvard.edu> wrote: >> > I don't think we're doing anything unusual. Here's the relevant snippet >> from >> > the generated IR for ccall (after instrumentation): >> > >> > ccall: ; preds = %pass6, %113 >> > %114 = phi i8* [ %110, %113 ], [ %108, %pass6 ] >> > %115 = inttoptr i64 %17 to i64* >> > %116 = bitcast i8* %69 to i32*, !dbg !7 >> > %117 = bitcast i8* %114 to i32 (i32*, i64, i64)*, !dbg !7 >> > store i64 %_msret13, i64* getelemen...

...I don't think we're doing anything unusual. Here's the relevant > snippet > >>> > from > >>> > the generated IR for ccall (after instrumentation): > >>> > > >>> > ccall: ; preds = %pass6, > >>> > %113 > >>> > %114 = phi i8* [ %110, %113 ], [ %108, %pass6 ] > >>> > %115 = inttoptr i64 %17 to i64* > >>> > %116 = bitcast i8* %69 to i32*, !dbg !7 > >>> > %117 = bitcast i8* %114 to i32 (i32*, i64, i64)*,...

How is ccall() implemented? If it manually sets up a stack frame, then it also needs to store argument shadow values in paramtls. I don't think there is an overflow, unless you have a _lot_ of arguments in a function call. On Sun, Feb 2, 2014 at 9:26 AM, Keno Fischer <kfischer at college.harvard.edu> wrote: > Also, I was looking at the instrumented LLVM code and I noticed that the

...TA device ses0: phy 0: parent 500304800182f4ff addr 500304800182f4ef ses0: probe13,pass5,da4: Element descriptor: 'Slot 05' ses0: probe13,pass5,da4: SAS Device Slot Element: 1 Phys at Slot 4 ses0: phy 0: SATA device ses0: phy 0: parent 500304800182f4ff addr 500304800182f4f0 ses0: probe14,pass6,da5: Element descriptor: 'Slot 06' ses0: probe14,pass6,da5: SAS Device Slot Element: 1 Phys at Slot 5 ses0: phy 0: SATA device ses0: phy 0: parent 500304800182f4ff addr 500304800182f4f1 SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Timecounter "TSC-low&qu...

Hi. No biggie, but when I remove a umass device it appears that two kernel messages are being written at the same time. (da4:umass-sim1:1:0:0): lost device - 0 outstanding, 1 refs (da4:(pass6:umass-sim1:1:umass-sim1:1:0:0:0): removing device entry 0): passdevgonecb: devfs entry is gone (FreeBSD 9.1-PRERELEASE #0 r241067) Cheers Michiel

Hello, I have no idea how to implement the following scenario apart from running two instances of samba on the same machine... I need a setup where two different Windows users will authen- ticate with two different passwords but get mapped to the same unix user. That is JOE got password PASS1 and maps to unix user joe with uid 1000 and JACK got password PASS2 and maps to unix user joe with

...chi HDS722020ALA330 JKAOA28A> at scbus4 target 0 lun 0 (pass3,ada3) <Hitachi HDS722020ALA330 JKAOA28A> at scbus5 target 0 lun 0 (pass4,ada4) <Hitachi HDS722020ALA330 JKAOA28A> at scbus6 target 0 lun 0 (pass5,ada5) <Hitachi HDS722020ALA330 JKAOA28A> at scbus7 target 0 lun 0 (pass6,ada6) <ST380815AS 4.AAB> at scbus8 target 0 lun 0 (pass7,ada7) <TSSTcorp CDDVDW SH-S223C SB01> at scbus9 target 0 lun 0 (cd0,pass8) <WDC WD1600AAJS-75M0A0 02.03E02> at scbus10 target 0 lun 0 (pass9,ada8) I'm not yet sure if the drive is fully dead or not....

...eneric USB CF Reader 1.01> at scbus2 target 0 lun 1 (da3,pass3) <Generic USB SM Reader 1.02> at scbus2 target 0 lun 2 (da4,pass4) <Generic USB MS Reader 1.03> at scbus2 target 0 lun 3 (da5,pass5) <PLEXTOR DVDR PX-750A 1.01> at scbus4 target 0 lun 0 (cd0,pass6) <HL-DT-ST DVD-ROM GDR8164B 0L06> at scbus4 target 1 lun 0 (cd1,pass7) -- Alex Dupre