On Tuesday, 18 September 2018 at 01:39:51 UTC, Nicholas Wilson
wrote:
On Tuesday, 18 September 2018 at 00:25:33 UTC, Sobaya wrote:
I'm waiting for the update. How's your progress?
I t appears I have broke SPIR-V completely somewhere along the
line, I may release a v0.2 with out it, hopefully
On Tuesday, 18 September 2018 at 00:24:23 UTC, SrMordred wrote:
Yes, i'm using signal(SIGSEGV, sigfn_t func), it catches
correctly, but end the execution after.
I find the alternatives of setjmp/longjmp and sigaction, but
none are avaliable on windows afaik.
setjmp/longjmp are available on
On Sunday, 10 June 2018 at 17:59:12 UTC, Joe wrote:
That worked but now I have a more convoluted case: a C array of
pointers to int pointers, e.g.,
int **xs[] = {x1, x2, 0};
int *x1[] = {x1a, 0};
int *x2[] = {x2a, x2b, 0};
...
int x2a[] = { 1, 3, 5, 0};
Only the first line is exposed (and with
On Tuesday, 18 September 2018 at 00:25:33 UTC, Sobaya wrote:
I'm waiting for the update. How's your progress?
I t appears I have broke SPIR-V completely somewhere along the
line, I may release a v0.2 with out it, hopefully within the week.
On Tuesday, 18 September 2018 at 00:25:33 UTC, Sobaya wrote:
On Friday, 7 September 2018 at 10:53:25 UTC, Sobaya wrote:
On Friday, 7 September 2018 at 10:17:47 UTC, Nicholas Wilson
wrote:
On Friday, 7 September 2018 at 06:45:32 UTC, Sobaya wrote:
[...]
You're missing an "m" in "nvvm", dunno
On Tuesday, 18 September 2018 at 00:24:23 UTC, SrMordred wrote:
On Tuesday, 18 September 2018 at 00:12:35 UTC, Diederik de
Groot wrote:
On Monday, 17 September 2018 at 23:44:41 UTC, SrMordred wrote:
[...]
You can use core.stdc.signal
nothrow @nogc @system sigfn_t signal(SIGSEGV, sigfn_t func)
On Friday, 7 September 2018 at 10:53:25 UTC, Sobaya wrote:
On Friday, 7 September 2018 at 10:17:47 UTC, Nicholas Wilson
wrote:
On Friday, 7 September 2018 at 06:45:32 UTC, Sobaya wrote:
[...]
You're missing an "m" in "nvvm", dunno if that will fix it.
[...]
I'll be adding these to DComput
On Tuesday, 18 September 2018 at 00:12:35 UTC, Diederik de Groot
wrote:
On Monday, 17 September 2018 at 23:44:41 UTC, SrMordred wrote:
[...]
You can use core.stdc.signal
nothrow @nogc @system sigfn_t signal(SIGSEGV, sigfn_t func)
To catch the signal
With a handler signature of:
enum void funct
On Monday, 17 September 2018 at 23:44:41 UTC, SrMordred wrote:
Its possible to use setjmp/longjmp on windows?
Or, to be straight to my problem: its possible to continue
execution after a SIGSEGV(or any other failure/signal) with
betterC and windows?
You can use core.stdc.signal
nothrow @nogc
Its possible to use setjmp/longjmp on windows?
Or, to be straight to my problem: its possible to continue
execution after a SIGSEGV(or any other failure/signal) with
betterC and windows?
On Monday, September 17, 2018 7:43:21 AM MDT Kagamin via Digitalmars-d-learn
wrote:
> try dpp https://github.com/atilaneves/dpp
Since according to Mike's post, it's C++ code, dpp wouldn't help, because it
currently only supports C and not C++.
- Jonathan M Davis
On Sunday, 16 September 2018 at 14:45:08 UTC, Vladimir Panteleev
wrote:
On Sunday, 16 September 2018 at 14:12:27 UTC, Guillaume Piolat
wrote:
Anyone has any information about the ABI of delegates?
In particular how to call them with a particular "this"/frame
pointer?
To solve a hairy problem
On Friday, 14 September 2018 at 20:52:42 UTC, H. S. Teoh wrote:
Whoa. After seeing the insane mess that is the Windows
pathname syntax, I'm so glad I code on Linux instead!
Yeah, also SIGPIPE, EINTR and "fork should be fast enough".
try dpp https://github.com/atilaneves/dpp
14 matches
Mail list logo
