Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] [cfe-dev] disabled Sema/ms-inline-asm.c test"
2008 Nov 07
0
[LLVMdev] [cfe-commits] r58509 - in /cfe/trunk: include/clang/Basic/DiagnosticKinds.def lib/AST/Expr.cpp lib/Sema/Sema.h lib/Sema/SemaExprCXX.cpp lib/Sema/SemaInherit.cpp lib/Sema/SemaInherit.h lib/Sema/SemaOverload.cpp test/SemaCXX/condition.cpp
On 2008-11-04, at 08:12, Sebastian Redl wrote:
> Mike Stump wrote:
>> On Nov 3, 2008, at 1:39 PM, Sebastian Redl wrote:
>>>> svn help cl
>>>>
>>>> [ runs away, much the same way someone that throws a lighted match
>>>> into a pool of gasoline ]
Probably wise.
>>> "cl": unknown command.
>>
>> From svn 1.5:
2017 May 30
2
Communication between Clang Sema and the Clang Codegen...
Hi All,
We have populated info in the Clang Sema i.e class Sema
(include/clang/Sema/Sema.h) and like to propagate the same to Clang
Codegen .
Currently we are propagating through ASTContext ,where we have
duplicating fields info and operation in the Sema and ASTContext .
Any better way of doing the same ?
Thank you
~Umesh
2013 Aug 14
1
[LLVMdev] [PATCH] fix corruption in X86AsmParser
This fixes the failing x86_errors.s test.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
---
diff -ru test/lib/Target/X86/AsmParser/X86AsmParser.cpp llvm-toolchain-3.3-3.3/lib/Target/X86/AsmParser/X86AsmParser.cpp
--- test/lib/Target/X86/AsmParser/X86AsmParser.cpp 2013-05-05 02:40:33.000000000 +0200
+++ llvm-toolchain-3.3-3.3/lib/Target/X86/AsmParser/X86AsmParser.cpp
2010 Sep 07
0
[LLVMdev] MS VS2008 build fails - X86AsmParser
On Sep 6, 2010, at 10:50 PM, David Shipman wrote:
> Hi all,
>
> Just tried to build from svn sources with Visual Studio 2008, mostly
> OK but fails
> building the X86AsmParser lib -
>
> I see a few commits from yesterday that may have something to do with it, but no
> idea what the solution is.
Wow, that's a pretty terrible diagnostic. Does r113198 help?
-Chris
2010 Sep 07
3
[LLVMdev] MS VS2008 build fails - X86AsmParser
Hi all,
Just tried to build from svn sources with Visual Studio 2008, mostly
OK but fails
building the X86AsmParser lib -
I see a few commits from yesterday that may have something to do with it, but no
idea what the solution is.
-David
See MSVC's beautiful and concise output below;
Compiling...
X86AsmParser.cpp
C:\dev\MSVisualStudio\VC\include\xutility(313) : error C2664: 'bool
2012 May 13
1
[LLVMdev] Unable to link in X86AsmParser.cpp into lli
Hi,
Using the trunk of svn. I'm trying to get inline-asm working on X86.
So I added call to:
> InitializeNativeTargetAsmParser()
during initialization. However, this causes a linking error:
> llvm[2]: Linking Debug+Asserts executable lli
> /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function
2013 Jul 16
0
[LLVMdev] [PATCH 2/2] X86: infer immediate forms of bit-test instructions
The instruction mnemonics for the immediate forms of bit-test
instructions including bt, btr and bts, btc do not work. llvm-mc barfs
with:
error: ambiguous instructions require an explicit suffix
This is highly user-unfriendly, since we can easily infer what the user
meant by inspecting $imm and translating the instruction appropriately.
Do it exactly as the Intel manual describes. Note that
2014 Apr 08
2
[LLVMdev] 3.4.1 Release Plans
On Tue, Apr 08, 2014 at 04:08:13PM +0400, Robert Khasanov wrote:
> Hi Reid,
>
> Would you approve your patches r203146 and r202774 to be backported to
> 3.4.1? They fix stability issues in x86 asm.
>
Hi Robert,
I was able to merge r203146, but it used a c++11 feature:
std::string::back() which I replaced with
std::string::at(std::string::size() - 1).
r202774 was not merged,
2010 Jul 26
2
[LLVMdev] LLVM Dependency Graph
Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows.
digraph G {
ipo
2014 Jun 26
2
[LLVMdev] problem with X86's AVX assembler?
On Thu, Jun 26, 2014 at 10:23 AM, Adam Nemet <anemet at apple.com> wrote:
>
>
> On Jun 25, 2014, at 7:05 PM, Jun Koi <junkoi2004 at gmail.com> wrote:
>
>
>
>
> On Thu, Jun 26, 2014 at 5:47 AM, Adam Nemet <anemet at apple.com> wrote:
>
>> Hi Jun,
>>
>> On Jun 25, 2014, at 8:14 AM, Jun Koi <junkoi2004 at gmail.com> wrote:
>>
2012 May 09
0
[LLVMdev] JIT support for inline asm on Linux
Resending, any pointers are much appreciated.
On 5/7/2012 11:16 PM, Ashok Nalkund wrote:
>
>
> On 5/7/2012 10:17 PM, Bendersky, Eli wrote:
> <snip>
>>>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc
>>>> LLVM ERROR: Inline asm not supported by this streamer because we don't
>>>> have an asm parser for this
2011 Mar 09
0
[LLVMdev] Unable to build latest with Visual Studio 2008
Hello,
I've been building Clang under Windows 7 and Visual Studio 2008 for a while
now, but had not touched it in a few months. Last night I wiped my build tree
to do a full rebuild with the latest version, and got the identical error as
David Shipman was seeing last September. Are others able to build under VS9
right now?
Thanks,
John
> Subject: Re: [LLVMdev] MS VS2008 build fails -
2012 May 08
2
[LLVMdev] JIT support for inline asm on Linux
On 5/7/2012 10:17 PM, Bendersky, Eli wrote:
<snip>
>>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc
>>> LLVM ERROR: Inline asm not supported by this streamer because we don't
>>> have an asm parser for this target
>>
>> I also tried other variations of the call with the same result:
>>> $lli
2014 Jun 26
2
[LLVMdev] problem with X86's AVX assembler?
On Thu, Jun 26, 2014 at 5:47 AM, Adam Nemet <anemet at apple.com> wrote:
> Hi Jun,
>
> On Jun 25, 2014, at 8:14 AM, Jun Koi <junkoi2004 at gmail.com> wrote:
>
> > Hi,
> >
> > I am trying to assemble below instruction with latest LLVM code, but
> fail. Am I doing something wrong, or is this a bug?
> >
> >
> > $ echo "vaddps zmm7
2015 Jul 23
2
[LLVMdev] Intel asm syntax and variable names
Hi all,
I've encountered an issue with x86 Intel asm syntax when using certain variable names.
If you look at the following example, where I try to do a mov to a memory location named "flags2", llvm- mc works fine:
>cat test_good.s
mov eax, flags2
>llvm-mc.exe -x86-asm-syntax=intel test_good.s -o -
.text
movl flags2, %eax
But if the memory location is
2014 Jun 25
2
[LLVMdev] problem with X86's AVX assembler?
Hi,
I am trying to assemble below instruction with latest LLVM code, but fail.
Am I doing something wrong, or is this a bug?
$ echo "vaddps zmm7 {k6}, zmm2, zmm4,
{rd-sae}"|./Release+Asserts/bin/llvm-mc -assemble -triple=x86_64 -mcpu=knl
-show-encoding -x86-asm-syntax=intel
.text
<stdin>:1:31: error: unknown token in expression
vaddps zmm7 {k6}, zmm2, zmm4, {rd-sae}
2020 Jan 21
2
MASM & RIP-relative addressing
Hi all,
Continuing work on llvm-ml (a MASM assembler)... and my latest obstacle is
in enabling MASM's convention that (unless specified) all memory location
references should be RIP-relative. Without it, we emit the wrong
instructions for "call", "jmp", etc., and anything we build fails at the
linking stage.
My best attempt at this so far is a small patch to
2015 Jul 23
0
[LLVMdev] Intel asm syntax and variable names
Suppose I have a global variable named 'EAX'. How do Intel assemblers
normally escape register names to access such a global variable?
On Thu, Jul 23, 2015 at 1:42 AM, Yatsina, Marina <marina.yatsina at intel.com>
wrote:
> Hi all,
>
>
>
> I’ve encountered an issue with x86 Intel asm syntax when using certain
> variable names.
>
>
>
> If you look at
2015 Jul 23
2
[LLVMdev] Intel asm syntax and variable names
Microsoft assembler treats mov to EAX as a register, even if there is a global memory also named EAX – meaning the register takes precedence.
But here I have a bit of a different situation – I have a global variable, which name happens to match an implicit register or a register that does not exist in the current arch, just in future ones. Microsoft assembler treats these cases as memory
2020 Jan 21
2
MASM & RIP-relative addressing
Apologies - I apparently remembered part of the issue incorrectly, so this
ended up quite confusing. The problem comes when referencing labels in a
different section of the binary. To clarify, if I assemble the code:
.data
foo BYTE 5
.code
mov eax, foo
with Microsoft's ml64.exe, it emits an object file disassembling to:
0: 8b 05 00 00 00 00 mov eax, dword ptr [rip]