search for: redstar

...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 > <http://redstar.de> > > Could I get some feedback on this? > I'm not sure if the emitting of the register names will effect msvc. > > Many Thanks > > Martell Malone > > _______________________________________________ > LLVM...

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 msvc. Many Thanks Martell Malone -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140415/70489003/att...

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; ple...

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...

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! Regards Kai -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: tls20120101.diff URL:

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)

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. >> Implemented is the implicit TLS model (__declspec(thread) in Visual C++). >> Please review. Thanks! > > Rough review: looks like the patch...

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

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

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:

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. All links are currently out-of-date. The following pages need >> updates: >> >> On page http://www.llvm.org/Users.html, please replace the existing e...

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).is...

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_EXCEPT...

Hi Rafael, is more approval needed to commit? Regards, Kai On 12.12.2013 00:56, Rafael Espíndola wrote: > 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 c...

On 12 December 2013 14:01, Kai Nacke <kai.nacke at redstar.de> wrote: > Hi Rafael, > > is more approval needed to commit? No, go for it. Cheers, Rafael

hi all - thoughts or pointes to the procedure for above... rich

Hi! I am still working on the Win64 EH code and now have a pretty usable result. (The MC part is already posted to llvm-commits, the other part follows soon. If you are curious the whole patch is here: http://www.redstar.de/ldc/win64eh_all_20130524.diff.) However, in one case I have a problem with LLVM being too smart. Consider the following D code: void doIt() { printf("doIt: start\n"); try { printf("doIt: try\n"); throw new Exception("Failure");...

You need to get the LLVM Sphinx docs using SVN or Git. If you want it, I can do the changes for you since I have already everything in place. -- Mikael 2013/12/3 Kai Nacke <kai at redstar.de> > 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...

...about generalizing LLVM exception handling probably means that I will need to do some work learning about how exception handling is currently implemented. Do you have a link to the patch your discussing, or a revision number? Thanks, JB On Fri, Jan 31, 2014 at 6:41 AM, Kai Nacke <kai.nacke at redstar.de> wrote: > Hi Jb, Hi Tong, > > with my patch LLVM emits unwind information for Windows 64bit. The Dwarf > EH encoding is used language specific data. That is the same way gcc > implements SEH for Windows 64bit. (As a side note, PR18546 now contains a > patch for Clang to use...

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 Compi...