search for: isstatement

tailcall optimization stop working in jit (lli) in revision 45527. i guess this is because the jit is tailjmping to the wrong function address. the following change would reenable tailcallopt in jit. But i am pretty sure that this is not the correct fix (since i don't really understand what is going on :). maybe evan can comment on this? regards arnold Index:

...neFragmentHeader{ .RelocOffset = 0, .RelocSegment = 5, .Flags = LineFlags{ .LF_HaveColumns = true, .unused = 0 }, .CodeSize = 52 } has column: true LineBlockFragmentHeader{ .NameIndex = 0, .NumLines = 6, .BlockSize = 84 } LineNumberEntry{ .Offset = 0, .Flags = 101 } Flags{ .Start = 101, .End = 17, .IsStatement = false } <snip some LineNumberEntry's> ColumnNumberEntry{ .StartColumn = 5, .EndColumn = 0 } ColumnNumberEntry{ .StartColumn = 30, .EndColumn = 0 } unknown bytes: f2 00 00 00 f0 00 00 00 LineFragmentHeader{ .RelocOffset = 64, .RelocSegment = 5, .Flags = LineFlags{ .LF_HaveColumns = true...

...ment = 5, .Flags = >> LineFlags{ .LF_HaveColumns = true, .unused = 0 }, .CodeSize = 52 } >> has column: true >> LineBlockFragmentHeader{ .NameIndex = 0, .NumLines = 6, .BlockSize = 84 } >> LineNumberEntry{ .Offset = 0, .Flags = 101 } Flags{ .Start = 101, .End = >> 17, .IsStatement = false } >> <snip some LineNumberEntry's> >> ColumnNumberEntry{ .StartColumn = 5, .EndColumn = 0 } >> ColumnNumberEntry{ .StartColumn = 30, .EndColumn = 0 } >> unknown bytes: f2 00 00 00 f0 00 00 00 >> LineFragmentHeader{ .RelocOffset = 64, .RelocSegment =...

Evan Cheng wrote: > I don't think so. Contribution welcome! :-) LLVM debugging support > isn't anywhere near where it needs to be. > Well, here's a rough sketch of what I was thinking of: class DebugInfoBuilder { public: /// Constructor DebugInfoBuilder(); /// Return the type defined by llvm.dbg.anchor.type StructType * GetAnchorType() const; ///

Hi Elena, On Thu, Mar 1, 2012 at 8:28 PM, Demikhovsky, Elena <elena.demikhovsky at intel.com> wrote: > Even if you explicitly specify –stack-alignment=16 the aligned movs are > still generated. > > It is not an issue related to ABI. This looks like PR10841, explanation and the way to solve it: http://llvm.org/bugs/show_bug.cgi?id=10841 Cheers, -- Bruno Cardoso Lopes

I have installed samba4wins with samba 3.0.21 and I don?t know how to configure it (I tried what says the howto.txt but it didnt work). I wanted to know if someone has alredy used samba4wins and made it work. In that case please contact me, so I can ask you some questions. Thank you Gabriela

Are there any utility classes, similar to IRBuilder, for creating source level debugging info? -- Talin

I don't think so. Contribution welcome! :-) LLVM debugging support isn't anywhere near where it needs to be. Evan On May 20, 2008, at 9:53 PM, Talin wrote: > Are there any utility classes, similar to IRBuilder, for creating > source > level debugging info? > > -- Talin > > _______________________________________________ > LLVM Developers mailing list >

On Fri, Mar 02, 2012 at 12:18:19AM -0300, Bruno Cardoso Lopes wrote: > Hi Elena, > > On Thu, Mar 1, 2012 at 8:28 PM, Demikhovsky, Elena > <elena.demikhovsky at intel.com> wrote: > > Even if you explicitly specify –stack-alignment=16 the aligned movs are > > still generated. > > > > It is not an issue related to ABI. > > This looks like PR10841,

I installed samba4wins on two of my Fedora Core 3 servers (from src rpm), on one PDC (samba 3.0.21c) and on one standalone server without samba, in order to test samba4wins. I think I managed to install and to setup properly the software but it seems nmblookup is not working on the PDC samba: [user]$ nmblookup '*' querying * on 192.168.19.255 name_query failed to find name *

Even if you explicitly specify –stack-alignment=16 the aligned movs are still generated. It is not an issue related to ABI. See my original mail: ./llc -mattr=+avx -stack-alignment=16 < basic.ll | grep movaps | grep ymm | grep rbp vmovaps -176(%rbp), %ymm14 vmovaps -144(%rbp), %ymm11 vmovaps -240(%rbp), %ymm13 - Elena From: Cameron McInally