On Sunday, 17 July 2016 at 05:07:00 UTC, Basile B. wrote:
On Saturday, 16 July 2016 at 20:13:00 UTC, Seb wrote:
On Friday, 15 July 2016 at 08:40:02 UTC, Arafel wrote:
Just as a follow-up, I think it's looking more and more like
a compiler bug. It works properly both with gdc and ldmd2.
Should
On Saturday, 16 July 2016 at 20:13:00 UTC, Seb wrote:
On Friday, 15 July 2016 at 08:40:02 UTC, Arafel wrote:
Just as a follow-up, I think it's looking more and more like a
compiler bug. It works properly both with gdc and ldmd2.
Should I make a bug report about that?
Yes please.
Hi, you
On Friday, 15 July 2016 at 08:40:02 UTC, Arafel wrote:
Just as a follow-up, I think it's looking more and more like a
compiler bug. It works properly both with gdc and ldmd2. Should
I make a bug report about that?
Yes please.
Just as a follow-up, I think it's looking more and more like a
compiler bug. It works properly both with gdc and ldmd2. Should I
make a bug report about that?
Hi!
I've stumbled across the following problem: when I raise an
exception from a (statically linked) library that was compiled
with -fPIC, I get a segmentation fault. Example:
-- libfoo/dub.json
{
"name" : "foo",
"description" : "Exception raising lib",
"dflags" : [
