Displaying 20 results from an estimated 8000 matches similar to: "[LLVMdev] MCSection and Win64 Exception Handling"
2011 May 20
1
[LLVMdev] LLVMdev Digest, Vol 83, Issue 33
I have a few pass managers, but only one of them has been initialized with
addPassesToEmitCode, how do I find how many passes are added to a function
pass manager ?
Thank you,
Xin
On Fri, May 20, 2011 at 1:00 PM, <llvmdev-request at cs.uiuc.edu> wrote:
> Send LLVMdev mailing list submissions to
> llvmdev at cs.uiuc.edu
>
> To subscribe or unsubscribe via the World Wide
2012 Aug 04
1
[LLVMdev] [cfe-dev] GCC 4.7.2 will have Win64 SEH (by default)
+LLVMdev
On Aug 4, 2012, at 9:45 AM, João Matos wrote:
> Charles Davis did a lot of work on Win64 SEH support in LLVM, check commits r131652-r132880.
>
> As I haven't tested it yet, what exactly is broken?
It's not finished yet. All the stuff for assembly code that uses Win64 EH is done, but not the code-gen-side stuff (cf. Win64Exception class in CodeGen). I was about to
2014 Apr 18
3
[LLVMdev] [PATCH] Seh exceptions on Win64
In summary we have no less than six patches required to support Win64 SEH
MinGW. The first five could be committed after review and LGTM but the last
one also requires Ray Donnelly approval.
Please comment in the Phabricator so the comments would be kept in context.
'unreachable' trap
http://reviews.llvm.org/D3417
Win64 SEH (LLVM)
http://reviews.llvm.org/D3418
Win64 SEH (clang)
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
On Nov 25, 2011, at 2:22 PM, bigcheesegs at gmail.com wrote:
> In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it.
Huh. It only seems to happen with a Windows triple or a Linux triple. Doesn't happen with a Mac triple, though--probably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in
2011 Nov 26
1
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
On Fri, Nov 25, 2011 at 1:47 PM, Charles Davis <cdavis at mymail.mines.edu> wrote:
>
> On Nov 25, 2011, at 2:22 PM, bigcheesegs at gmail.com wrote:
>
>> In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it.
> Huh. It only seems to happen with a Windows triple or a Linux triple. Doesn't happen with a Mac triple,
2011 Nov 25
2
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it.
Sent from my iPhone
On Nov 25, 2011, at 2:15 PM, Charles Davis <cdavis at mymail.mines.edu> wrote:
>
> On Nov 25, 2011, at 8:39 AM, Michael Spencer wrote:
>
>> So I was taking a look at Microsoft C++ ABI support while on vacation,
>> and ran into a major
2010 Feb 14
0
[LLVMdev] Unable to compile .s files generated with llc.
Van Dijck, Tom wrote:
> Hey,
>
> I've been trying this for a couple days now, finding different assemblers and trying different options but I can't figure it out..
> I must be missing something very obvious.
>
> I got a simple "hello world" app in llvm, making the .bc file using 'llvm-as test.llvm -o=test.bc' works fine.
> then I can use llvm-ld to
2006 Feb 14
1
Win64 problems
I am having problems with my program decoding .ogg files on the Win64 platform and am wondering if this is a known issue or not.
I have tried using the prebuilt .dll's, the static .lib's and building from source (1.1.3) and I get the same results. My program is being compiled on a win32 platform, but the decoder fails if I run it on a win64 system.
Unfortunately this is being reported
2009 Jul 31
0
[LLVMdev] Win64 bugs
Hi Peter,
The attached patch is a workaround for the XMM misalignment issue. Basically
it uses the fallback method of saving and restoring registers on the stack,
which does work correctly with alignment. If I recall correctly it also
doesn't save any registers unnecessarily, but I could be wrong about that.
Anyway, it's hack, but if all you want for now is to be able to work with
Win64
2009 Mar 04
1
[LLVMdev] Bug in x86-64/Win64 Calling Convention
Hello,
I think I've found a bug in the calling convention support for X86-64/
Win64. It doesn't correctly save and restore the XMM registers in
the function prolog/epilog. (The problem only exists on Win64, since
Linux and Mac OS use calling convention in which these registers are
volatile and not callee-saved.)
X86RegisterInfo::getCalleeSavedRegs() when called for a Win64
2009 Dec 04
0
[LLVMdev] Win64 Calling Convention problem
Thanks, Anton!
I didn't know about exceptions like _Complex that you mentioned. The
only way to support them is to place the burden of correct parameter
passing on the front-end, I understand that now.
So, today I created a new transformation pass that makes sure that
LLVM IR, which works alright with the default Win32 calling
conventions, also plays nice with Win64 code within the limited
2009 Jul 31
0
[LLVMdev] Win64 bugs
On Thu, Jul 30, 2009 at 5:32 PM, Peter Shugalev<peter at shugalev.com> wrote:
> Hello!
>
> I've just tried generating Win64 code and the result is not that good.
>
> First of all, XMM registers are saved without reason to do so. Not only
> this slows the performance but leads to random crashes too. XMMs are
> stored to the stack with MOVAPS instruction which requires
2014 Apr 18
2
[LLVMdev] [PATCH] Seh exceptions on Win64
Hi Chandler,
There were five SEH releated patches posted in two threads in the last days.
Two different patches in Martell e-mail starting this thread: the win64 seh
(llvm) and the register names
Three more related SEH patches in another thread: one for win64 seh clang,
one for MinGW toolchain and another for unreachable prologue.
To clarify and allow proper reviews for the different patches I
2011 Mar 10
1
[LLVMdev] host triple for Win64?
What host triple should I be using to specifically target x86_64 /
Win64? I notice there is no Win64 in the OSType enum, but there is
Win32. And yet I know llvm can target Win64, right?
--
Eric Niebler
BoostPro Computing
http://www.boostpro.com
2012 Oct 23
4
building libtheora 1.0 on win64
I have an old conferencing app that uses theora and I'm building it for
win64.
libthora 1.1 builds just fine, but libtheora 1.0 has errors related to
assembly code when building for x64.
I've tried using 1.1, but the video does not look right -- the clients all
generate their own first 3 packets instead of sending them over the network
since they assume they are all on the same version
2010 Feb 14
3
[LLVMdev] Unable to compile .s files generated with llc.
Hey,
I've been trying this for a couple days now, finding different assemblers and trying different options but I can't figure it out..
I must be missing something very obvious.
I got a simple "hello world" app in llvm, making the .bc file using 'llvm-as test.llvm -o=test.bc' works fine.
then I can use llvm-ld to make an executable which then runs fine (although not
2010 Nov 25
2
[LLVMdev] Is the Win64 codegen issue fixed?
Great! Are there other issues I should be aware of?
Félix
Le 2010-11-25 à 07:43:23, Anton Korobeynikov a écrit :
> Hello Felix
>
>> I have a project in mind that involves using the JIT for a few targets (x86
>> and x86_64 processors on Mac OS, Linux and Windows). However, there is an
>> open bug that says LLVM generates incorrect code for Win64.
>> Eli's last
2010 Nov 25
2
[LLVMdev] Is the Win64 codegen issue fixed?
Hello guys,
I have a project in mind that involves using the JIT for a few targets (x86 and x86_64 processors on Mac OS, Linux and Windows). However, there is an open bug that says LLVM generates incorrect code for Win64.
Eli's last comment on the bug, however, says that it appears to be fixed.
I don't have a Win64 box to test it. Can someone confirm that it now works (or still
2012 Sep 12
2
[LLVMdev] State of Win64 exceptions?
Hi again,
Can anyone tell me about the state of Win64 exceptions?
I've noticed that there are a good few related patches since the release of
3.1. Is it working now?
Is it likely 3.2 will support Win64 exceptions?
Cheers.
- Manu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Jul 31
2
[LLVMdev] Win64 bugs
On 30-Jul-09, at 8:54 PM, Eli Friedman wrote:
> On Thu, Jul 30, 2009 at 5:32 PM, Peter Shugalev<peter at shugalev.com>
> wrote:
>> Though the most problematic stuff is the lack of 'shadow zone'
>> support
>> in Win64 ABI. Or maybe I haven't figured out how to turn this on. In
>> Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h