Displaying 11 results from an estimated 11 matches for "isstatic".
Did you mean:
sstatic
2008 Jan 03
2
[LLVMdev] Tailcall optimization in jit stopped working
...=======
--- lib/Target/X86/X86CodeEmitter.cpp (revision 45541)
+++ lib/Target/X86/X86CodeEmitter.cpp (working copy)
@@ -601,7 +601,8 @@
if (MO.isMachineBasicBlock()) {
emitPCRelativeBlockAddress(MO.getMBB());
} else if (MO.isGlobalAddress()) {
- bool NeedStub = !IsStatic ||
+ bool NeedStub = Opcode == X86::TAILJMPd || Opcode ==
X86::TAILJMPr ||
+ Opcode == X86::TAILJMPm || !IsStatic ||
(Is64BitMode && TM.getCodeModel() == CodeModel::Large);
emitGlobalAddress(MO.getGlobal(), X86::reloc_pcrel_word,...
2018 Aug 31
2
PDB questions
Zachary,
Thanks for the help on IRC earlier. I've got code that can capture a stack
trace and then discover for each address, its module, function, source
index, line, and column.
I still have a couple of loose ends though. Do you know what's going on
here?
1. There appears to be 8 bytes before every LineFragmentHeader. Here's some
of my own debug output, which matches
2018 Aug 31
2
PDB questions
For the first and third questions, the easiest thing to do would be run
llvm-pdbutil under a debugger and step through the code. Code that looks
simple and innocuous can often have a lot of stuff hidden behind it. For
example you could step through that loop that iterates the debug
subsections and look at the value of Reader.getOffset() every time, and see
if it matches with your own code
2008 May 23
1
[LLVMdev] DebugInfoBuilder?
...it is
defined
const std::string & name, /// Name of the subprogram
const std::string & qualifiedName, /// Fully-qualified name
unsigned line, /// Line number
GlobalVariable * typeDesc, /// Type descriptor
bool isStatic, /// True if this has static
scope (internal to module)
bool isDefined); /// True if this is not
externally-defined.
/// Create a type descriptor for a primitive type
GlobalVariable * CreateBasicTypeDescriptor(
GlobalVariable * comp...
2012 Mar 02
0
[LLVMdev] Stack alignment on X86 AVX seems incorrect
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
2006 Mar 21
4
samba4wins
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
2008 May 21
2
[LLVMdev] DebugInfoBuilder?
Are there any utility classes, similar to IRBuilder, for creating source
level debugging info?
-- Talin
2008 May 21
0
[LLVMdev] DebugInfoBuilder?
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
>
2012 Mar 02
2
[LLVMdev] Stack alignment on X86 AVX seems incorrect
...ill 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
I was looking at this again today. What about the following approach:
(1) Change AllocaInst to compute the isStaticAlloca once and remember
it.
(2) Check all functions for
(a) static allocations with an alignment larger than the default stack
alignemnt
(b) dynamic alloca
(3) If (a) is present and not (b), use the frame pointer to address
arguments and the stack pointer to address local variab...
2006 Mar 10
1
samba4wins - all ok but how to use nmblookup from my PDC?
...llRetryInterval: 30
pushChangeCount: 0
pushUseInform: 0
type: 0x3
address: 192.168.19.109
Sama4wins is generating this kind of records:
# record 12
dn: name=USER,type=0x03
distinguishedName: name=USER,type=0x03
type: 0x03
name: USER
objectClass: winsRecord
recordType: 0
recordState: 0
nodeType: 0
isStatic: 0
expireTime: 20060313052429.0Z
versionID: 17
winsOwner: 192.168.19.109
address: 192.168.19.1;winsOwner:192.168.19.109;expireTime:20060313052429.0Z;
registeredBy: 192.168.19.1
--
Tel: +57 (2) 7314752/3222/2595 - Fax: +57 (2) 7310514
Carrera 31 #18-07 Parque Infantil - PO Box 1795 - Pasto
2012 Mar 01
3
[LLVMdev] Stack alignment on X86 AVX seems incorrect
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