search for: fpo

Hi Mike, On 2013-08-02 18:26, Michael Lewis wrote: > I've been working recently on a precise garbage collector which runs > alongside native code JITted by LLVM. Today marks the first time the > GC has passed its entire test suite as well as extensive soak tests in > non-trivial programs. I'm glad to hear that you solved the issues you described in your last mail. How did you

Hi all, I've been working recently on a precise garbage collector which runs alongside native code JITted by LLVM. Today marks the first time the GC has passed its entire test suite as well as extensive soak tests in non-trivial programs. It's been an interesting and educational process, to say the least, and I've run into quite a few things that might be useful to know for others

On Fri, Sep 8, 2017 at 9:00 AM Adrian Prantl <aprantl at apple.com> wrote: > > > Eventually, some tests will inevitably need to Windows or Posix > specific, so you're going to have to have all this extra stuff (the new > substitutions, the different command lines, the custom output formats, > etc. So I think something like this provides maximal encouragement of >

...m developing a novel language that has historically used LLVM for code generation, behind a custom self-hosted front-end. The runtime for this language offers a garbage collector. In the past I've been on 32-bit Windows where precise garbage collection is relatively straightforward (as long as FPO is disabled). Walking the stack is a simple bit of pointer chasing and some fixups. I've had a working GC on Win32 for years and actually posted here in the past about my experience with .gcroot and other related miscellany involved in building a real GC with LLVM. Recently I've decided t...

...ation of a Windows unwinder. Currently? As recent as LLVM 4.0, I don't think the JIT was fully capable of handling COFF files, and LLVM wouldn't emit the correct sections (with the COFF-formatted unwind tables) when used in ELF mode. The prolog is known to be standard since Julia disables FPO on all code, so the hand-coded values simply needed to declare that to the unwinder. Windows doesn't have epilog records (it instead infers them from the structure of the assembly itself, and requires that LLVM only generate function returns using a particular finite set of instructions), so th...

...:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x180e30,0x180788): stub > wine: Call from 0x7b839b12 to unimplemented function msvcp90.dll.?find@?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QBEIABV12 at I@Z, aborting > fixme:dbghelp_msc:pe_load_debug_directory This guy has FPO information > wine: Unimplemented function msvcp90.dll.?find@?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QBEIABV12 at I@Z called at address 0x7b839b12 (thread 0009), starting debugger... > Unhandled exception: unimplemented function msvcp90.dll.?find@?$basic_string a...

Hey guys, Is there a way to force the LLVM JIT compiler to omit the frame pointer in its generated i386/amd64 code? I've got a complex situation in which the stack can potentially be moved around so I'd prefer that the base pointer doesn't get pushed there. Félix

I am new to the list and I am interested in reviewing what might have been developed supporitng Speex for the Palm OS? I like the low end of 4 kbps for narrow or low frequency transmission. Regards "Dr. David" M. Holmes-Smith, OC, OSA, OG, MEd, MS, DD E. J. King School PSC 476, Box 9 FPO, AP 96322 (Sasebo Naval Base, Japan) <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the bod...

....exe. This is the message: Code: ... wine: Unhandled page fault on read access to 0xd12e3930 at address 0x41654d (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0xd12e3930 in 32-bit code (0x0041654d). fixme:dbghelp_msc:pe_load_debug_directory This guy has FPO information Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:0041654d ESP:0034f508 EBP:0034f620 EFLAGS:00010282( - 00 - RIS1) EAX:b6b1c731 EBX:7b8b0888 ECX:1ba00028 EDX:005805d0 ESI:0043a160 EDI:7ffdf000 Stack dump: 0x0034f508: 7ffdf000 0043a160 7b8b0888 401e93ec 0x003...

...n/X86/fp-intrinsics.ll > LLVM :: CodeGen/X86/splat-for-size.ll > LLVM :: CodeGen/X86/sse-scalar-fp-arith.ll > LLVM :: CodeGen/X86/vec_shift6.ll > LLVM :: CodeGen/X86/vector-compare-combines.ll > LLVM :: CodeGen/X86/vector-narrow-binop.ll > LLVM :: DebugInfo/COFF/vframe-fpo.ll > LLVM :: DebugInfo/X86/debug-info-static-member.ll > LLVM :: FileCheck/check-empty-tag.txt > LLVM :: FileCheck/dump-input-annotations.txt > LLVM :: FileCheck/no-multi-suffixes.txt > LLVM :: FileCheck/var-scope.txt > LLVM :: MC/AsmParser/expr-shr.s > LLVM :: MC...

> exactly Well, in general, there is no connection between the performance on x86 and on ARM. You can try to profile your code and find what causes the speedup on x86 and figure out the slowdowns on ARM. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

G''Day Folks, Check out this DTrace script, # ./swapinfo.d RAM _______Total 511 Mb RAM Unusable 8 Mb RAM Kernel 96 Mb RAM Locked 0 Mb RAM Used 318 Mb RAM Avail 88 Mb Disk _______Total 1023 Mb Disk Used 9 Mb Disk Avail 1014 Mb Swap _______Total 1367 Mb Swap Used 327

On Fri, Apr 10, 2009 at 5:24 PM, Devang Patel <dpatel at apple.com> wrote: > ... because usually a module pass operates on entire module (e.g. > inliner) and it does not require information specific to a function. > If your pass need info collected by a function pass then why not > structure your pass as a function pass and run it for all function in > a module ? I very much

Hello everyone, I was following the discussion, but I have to admit, that my skills aren't high enough to follow you guys. For my current exception problem, I don't have to stick around with the PECOFF format, so I used clang to don't compile to a PECOFF, but to a ELF file. Interesting, now I'm missing the functions: __cxa_allocate_exception __cxa_throw _ZTI I loaded the DLL

...to get a gl context for default adapter wine: Unhandled page fault on read access to 0x00000030 at address 0x7e2088a1 (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000030 in 32-bit code (0x7e2088a1). fixme:dbghelp_msc:pe_load_debug_directory This guy has FPO information Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7e2088a1 ESP:0032f860 EBP:0032f928 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:7e30ae00 ECX:00000000 EDX:00000000 ESI:7e22388d EDI:00000000 Stack dump: 0x0032f860: 0032f8b4 00000000 0000004c 7ef73de2 0x003...

Spoiler: the following only applies to Windows binary format handling. Potential for extending yaml2obj to support COFF debug directories<https://docs.microsoft.com/en-us/windows/win32/debug/pe-format#debug-directory-image-only> recently came up during a code review<https://reviews.llvm.org/D70606#1873185>. Currently, its COFF

...> > Currently? As recent as LLVM 4.0, I don't think the JIT was fully capable > of handling COFF files, and LLVM wouldn't emit the correct sections (with > the COFF-formatted unwind tables) when used in ELF mode. > > The prolog is known to be standard since Julia disables FPO on all code, > so the hand-coded values simply needed to declare that to the unwinder. > Windows doesn't have epilog records (it instead infers them from the > structure of the assembly itself, and requires that LLVM only generate > function returns using a particular finite set of...

...exiting the game This is the printout: wine: Unhandled page fault on read access to 0x016922c3 at address 0x4f9150 (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x016922c3 in 32-bit code (0x004f9150). fixme:dbghelp_msc:pe_load_debug_directory This guy has FPO information Register dump: ?CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b ?EIP:004f9150 ESP:0033c704 EBP:0033c730 EFLAGS:00010202( ? - 00 ? ? ?- -RI1) ?EAX:02931b40 EBX:00001fff ECX:00000001 EDX:00000001 ?ESI:016922c3 EDI:0033c730 Stack dump: 0x0033c704: ?02931b40 001ad108 004f9100 0053693e 0x003...

...e http protocol. shell32: Fix a leak in the ebrowser travellog (Valgrind). shell32/tests: Fix a leak in the ebrowser tests (Valgrind). Dylan Smith (1): richedit: Clear non-default style when changing to plain text mode. Eric Pouech (26): winedump: Added support for dumping FPO streams. dbghelp: Restructure internal PDB information. dbghelp: Use new file/debug format framework to allow keeping pdb files opened. dbghelp: Keep the mapping of any PDB file open until the module is unloaded. dbghelp: Added preliminary extended FPO information out of PDB...

...rically used LLVM for code >> generation, behind a custom self-hosted front-end. The runtime for this >> language offers a garbage collector. >> >> In the past I've been on 32-bit Windows where precise garbage collection >> is relatively straightforward (as long as FPO is disabled). Walking the >> stack is a simple bit of pointer chasing and some fixups. I've had a working >> GC on Win32 for years and actually posted here in the past about my >> experience with .gcroot and other related miscellany involved in building a >> real GC with...