similar to: [LLVMdev] [PATCH] TLS support for Windows 32+64bit

Displaying 20 results from an estimated 500 matches similar to: "[LLVMdev] [PATCH] TLS support for Windows 32+64bit"

2012 Jan 01
0
[LLVMdev] [PATCH] TLS support for Windows 32+64bit
On Sun, Jan 1, 2012 at 10:44 AM, Kai <kai at redstar.de> wrote: > Happy new year to all! > > The attached patch adds TLS support for x86_64-pc-win32 and x86-pc-win32. > Implemented is the implicit TLS model (__declspec(thread) in Visual C++). > Please review. Thanks! Rough review: looks like the patch is in the right direction; please take out all tabs, please take out all
2012 Jan 19
2
[LLVMdev] [PATCH] TLS support for Windows 32+64bit
Hi! I added 2 more tests and also refined an assert statement. Applies cleanly to r148473 now. Are there more comments on the code? Thank you!! Regards Kai On 01.01.2012 22:01, Eli Friedman wrote: > On Sun, Jan 1, 2012 at 10:44 AM, Kai<kai at redstar.de> wrote: >> Happy new year to all! >> >> The attached patch adds TLS support for x86_64-pc-win32 and x86-pc-win32.
2012 Jan 25
0
[LLVMdev] [PATCH] TLS support for Windows 32+64bit
On Thu, Jan 19, 2012 at 9:24 AM, Kai <kai at redstar.de> wrote: > Hi! > > I added 2 more tests and also refined an assert statement. Applies cleanly > to r148473 now. Are there more comments on the code? Thank you!! + assert(Inst.getOperand(0).isReg() && + (Inst.getOperand(ImmOp).isImm() || + (Inst.getOperand(ImmOp).isExpr() && +
2011 Dec 04
3
[LLVMdev] Implement implicit TLS on Windows - need advice
Hi! LLVM currently does not implement the implicit TLS model on Windows. This model is easy: - a thread local variable ends up in the .tls section - to access a thread local variable, you have to do (1) load pointer to thread local storage from TEB On x86_64, this is gs:0x58, on x86 it is fs:0x2C. (2) load pointer to thread local state. In general, the index is stored in variable
2011 Dec 06
0
[LLVMdev] Implement implicit TLS on Windows - need advice
On Sun, Dec 4, 2011 at 9:18 AM, Kai <kai at redstar.de> wrote: > Hi! > > LLVM currently does not implement the implicit TLS model on Windows. This > model is easy: > > - a thread local variable ends up in the .tls section > - to access a thread local variable, you have to do >  (1) load pointer to thread local storage from TEB >      On x86_64, this is gs:0x58, on
2014 Apr 15
10
[LLVMdev] [PATCH] Seh exceptions on Win64
Hi, I'd like to submit a patch to match the clang patch on the front end. http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140414/103257.html The front end doesn't need this patch to work but it's still important. This is mostly based on work done by kai from redstar.de Could I get some feedback on this? I'm not sure if the emitting of the register names will effect
2014 Apr 17
2
[LLVMdev] [PATCH] Seh exceptions on Win64
Hi, On 15.04.2014 23:44, Vadim Chugunov wrote: > Hi, > I am curious - how does clang deal with epilogue-less functions that > result from _Raise_Exception being marked 'noreturn'? > I've also been playing with Kai's patch, and discovered that this tends > to greatly confuse Windows stack unwinder in cases when noreturn call is > at the end of a function, so
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)
2012 Jul 27
3
[LLVMdev] Roundtrip clang -> llc -> clang fails
Hi! I am not sure if this is a bug or not. I have the following non-sense C module exc_alloc.c: #include <windows.h> void *AllocMem() { HANDLE heap = GetProcessHeap(); void *p = HeapAlloc(heap, HEAP_GENERATE_EXCEPTIONS | HEAP_ZERO_MEMORY, 16*1024*1014*1024); return p; } If I execute the following commands clang -S -emit-llvm -o exc_alloc.ll exc_alloc.c llc -filetype=asm
2013 Dec 11
2
[LLVMdev] Switching to the new MingW ABI
On 11 December 2013 05:41, Kai Nacke <kai.nacke at redstar.de> wrote: > Maybe we should also change the stack probing code. I think ___chkstk_ms is > used since gcc 4.6. It simplifies the prologue generation code a bit. I just checked gcc 4.6 and looks like you are right, it uses ___chkstk_ms. LGTM. We should probably commit this first, since it is common for gcc 4.6 and newer.
2014 Jan 27
2
[LLVMdev] Is addrspacecast implemented on Windows?
Hi all! On x86_64, segment prefix fs: is in address space 257 and gs: in address space 256. (BTW: are there constants for these magic values?) How can I use this in IR? I want to express this assembler code in IR: mov RAX, 8; mov RAX, GS:[RAX]; ret; I tried the following: define i64 @getStackBottom(i64 %addr) { entry: %ptr = inttoptr
2006 Jun 14
49
[Bug 464] state match sometimes failes RELATED,ESTABLISHED matches
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=464 ------- Additional Comments From holm@theorie.physik.uni-goettingen.de 2006-06-14 15:00 MET ------- I run into the same probs with Mandriva kernel. All kernel >2.6.11 are definitly affected. kernel 2.6.8.1 has no problems. Hope this helps a little bit. -- Configure bugmail:
2009 Sep 08
2
transition of vbox environments to xVN server
hi all - thoughts or pointes to the procedure for above... rich
2013 Dec 03
2
[LLVMdev] Please update LDC references on LLVM website
Hi Rafael, is there a repository with the static pages or should I simply produce a diff between the 2 versions? Regards, Kai On 03.12.2013 14:30, Rafael Espíndola wrote: > Can you send a patch? > > On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: >> Hi! >> >> I like to submit some updates to the LLVM website regarding the LDC >> compiler.
2014 Jan 31
3
[LLVMdev] Technical details discussion for SEH
Can you clarify what you mean by "real SEH handling"? My company has me looking at this in the hopes that I can make LLVM capable of building windows drivers. If you mean "visual c++ style SEH", I'm fairly sure that isn't necessary for my purposes, but it would be nice. If you mean "something that works at all," then your concern about generalizing LLVM
2013 Dec 02
3
[LLVMdev] Please update LDC references on LLVM website
Hi! I like to submit some updates to the LLVM website regarding the LDC compiler. All links are currently out-of-date. The following pages need updates: On page http://www.llvm.org/Users.html, please replace the existing entry "LLVM D Compiler" in section "Open Source Projects" with: <tr> <td><a href="http://wiki.dlang.org/LDC/">
2014 Jan 02
2
[LLVMdev] http://llvm.org/apt/precise/ broken for 3.4?
Hi all, I use the nightly builds of LLVM in my Travis CI configuration. Travis CI is based on Ubuntu 12.04 precise. Currently, I am not able to install llvm-3.4 and llvm-3.4-dev. The error is always: $ sudo apt-get install llvm-3.4 llvm-3.4-dev Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package llvm-3.4 E: Couldn't find any
2012 Jan 01
2
Some Doveadm Tools lack proper exit codes
Happy New Year Everyone, and *yes* it's that time of the year to archive old stuff again. Please implement proper error codes to support this (scripting) endeavor. => Good $ doveadm user foo userdb lookup: user foo doesn't exist $ echo $? 2 => Bad $ doveadm acl get -u tlx at leuxner.net FOO doveadm(tlx at leuxner.net): Error: Can't open mailbox FOO: Mailbox doesn't
2013 Dec 03
0
[LLVMdev] Please update LDC references on LLVM website
Can you send a patch? On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: > Hi! > > I like to submit some updates to the LLVM website regarding the LDC > compiler. All links are currently out-of-date. The following pages need > updates: > > On page http://www.llvm.org/Users.html, please replace the existing entry > "LLVM D Compiler" in section
2012 Jul 28
0
[LLVMdev] Roundtrip clang -> llc -> clang fails
On Fri, Jul 27, 2012 at 3:36 PM, Kai <kai at redstar.de> wrote: > Hi! > > I am not sure if this is a bug or not. > > I have the following non-sense C module exc_alloc.c: > > #include <windows.h> > > void *AllocMem() { > HANDLE heap = GetProcessHeap(); > void *p = HeapAlloc(heap, HEAP_GENERATE_EXCEPTIONS | > HEAP_ZERO_MEMORY,