search for: _abort

I am working on the MASM backend. I do not know what to do about '_write' and '_abort'. They seem to be added to a modules functions as externals even when they are not being used. They cannot just be remove just in case they are being used. What are they there for ? The only options I have are to scan the whole module for uses of them, or to provide library implementations fo...

On Wed, 6 Jul 2005, Aaron Gray wrote: > I am working on the MASM backend. > > I do not know what to do about '_write' and '_abort'. They seem to be > added to a modules functions as externals even when they are not being > used. Why is that a problem? > They cannot just be remove just in case they are being used. What are > they there for ? They are part of the exception handling support. > The only...

On Fri, Dec 16, 2011 at 12:17:32PM -0500, David Fang wrote: >>> These results have far fewer failures than svn-trunk, and are also >>> comparable to bootstrapping with gcc-4.6.2, summarized here: >>> http://paste.lisp.org/display/126363 >>> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >>> This consistency between

>> These results have far fewer failures than svn-trunk, and are also >> comparable to bootstrapping with gcc-4.6.2, summarized here: >> http://paste.lisp.org/display/126363 >> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >> This consistency between different bootstraps of the release gives me >> some hope that g++-4.0.1 is

...s\compiler\llvm-2.0\win32\release>llvm-ld -native hellow.bc a.out.s: Assembler messages: a.out.s:1: Error: unknown pseudo-op: `.686' a.out.s:2: Error: unknown pseudo-op: `.model' a.out.s:4: Error: no such instruction: `extern _puts:near' a.out.s:5: Error: no such instruction: `extern _abort:near' a.out.s:8: Error: invalid character '_' in mnemonic a.out.s:9: Error: no such instruction: `align 16' a.out.s:10: Error: invalid character '_' in mnemonic a.out.s:11: Error: too many memory references for `sub' a.out.s:12: Error: junk `PTR [ESP+10]' after expre...

2009/7/18 Chris Lattner <clattner at apple.com> > > On Jul 18, 2009, at 2:56 PM, Aaron Gray wrote: > > I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc > > > If you're iterating over functions, just ignore all intrinsics. > Okay, but it would be nice if the Module object reflected the lowered symbol names like 'memcpy' too.

...; preds = %whilecont13, %whilecont %lv14 = load i32* %lv ; <i32> [#uses=1] ret i32 %lv14 } And here is the assembly code I generated with "llc -march=x86 -x86-asm-sytax=intel filename". .686 .MMX .XMM .model flat EXTERN _abort:near .text public _foo ALIGN 16 _foo proc near sub ESP, 8 $label1: mov EAX, DWORD PTR [ESP + 12] mov DWORD PTR [ESP], EAX mov DWORD PTR [ESP + 4], 0 mov EAX, DWORD PTR [ESP] mov DWORD PTR [_gv], EAX cmp DWORD PTR [ESP], 6 jb $BB1_4 $BB1_1:...

On 30.03.16 14:28, Nir Soffer wrote: > On Wed, Mar 30, 2016 at 1:36 PM, Michal Skrivanek > <michal.skrivanek@redhat.com> wrote: > > > >> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones@redhat.com> wrote: > >> > >> On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote: > >>> Hi, > >>> > >>> We

This patch series introduces the tapback daemon, the user space daemon that acts as a device''s back-end, essentially most of blkback in user space. The daemon is responsible for coordinating the front-end and tapdisk. It creates tapdisk process as needed, instructs them to connect to/disconnect from the shared ring, and manages the state of the back-end. The shared ring between the