search for: d3417

Displaying 4 results from an estimated 4 matches for "d3417".

Did you mean: 3417
2014 Apr 18
2
[LLVMdev] [PATCH] Seh exceptions on Win64
...H 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 opened reviews for four of them (the fifth got LGTM in the discussion but it does have the ownership issue you wrote) D3417 Emit a trap instruction for IR 'unreachable <http://reviews.llvm.org/D3417> D3418 SEH exceptions on Win64 (LLVM) <http://reviews.llvm.org/D3418> D3419 SEH exceptions on Win64 (clang part) <http://reviews.llvm.org/D3419> D3420 MinGW toolchain <http://reviews.llvm.org/D342...
2014 Apr 18
2
[LLVMdev] [PATCH] Seh exceptions on Win64
Hi Chandler, Kai contributed the WIN64 SEH patch some time ago on llvm-commits: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20131118/196105.html it was never completed. Kai also responded in this thread. I opened a phabricator for the patch http://reviews.llvm.org/D3418 Yaron 2014-04-18 12:31 GMT+03:00 Chandler Carruth <chandlerc at google.com>: > > On Tue,
2014 Apr 18
3
[LLVMdev] [PATCH] Seh exceptions on Win64
...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) http://reviews.llvm.org/D3419 MinGW toolchain http://reviews.llvm.org/D3420 TLS (clang) http://reviews.llvm.org/D3421 Register names instead of numbers http://reviews.llvm.org/D3422 2014-04-18 14:42 GMT+03:00 Martell...
2014 Apr 15
2
[LLVMdev] Emit code for 'unreachable'
On Tue, Apr 15, 2014 at 2:14 PM, Vadim Chugunov <vadimcn at gmail.com> wrote: > I've looked through LLVM codegen code and found that > SelectionDAGBuilder::visitUnreachable() is basically a no-op. So I don't > see how it could have generated anything... > > What would be the right way to go about adding this functionality? > Right now I am thinking to add