On Saturday, 19 November 2016 at 16:43:40 UTC, thedeemon wrote:
> On Friday, 18 November 2016 at 11:02:20 UTC, Daniel Kozak wrote:
>>>>  Ubuntu 12.04 to 16.04 which has PIE enabled now, and there are problems with D on it.
>>>
>>> Where can I learn more about it?
>>>
>> It has been typo, it should not be 16.04 but 16.10.
>
> Err.. I mean, what is PIE and what kind of problems with D are there?

DMD emit relocation data that linker can't make sense of, that's what happens. So you can't link anything that wasn't compiled with -fPIC, even if you aren't using shared object, and the standard lib doesn't work.

On Saturday, 19 November 2016 at 22:19:58 UTC, deadalnix wrote:

>> Err.. I mean, what is PIE and what kind of problems with D are there?
>
> DMD emit relocation data that linker can't make sense of, that's what happens. So you can't link anything that wasn't compiled with -fPIC, even if you aren't using shared object, and the standard lib doesn't work.

Thanks!

On Thursday, 17 November 2016 at 17:49:09 UTC, sanjayss wrote:
> https://www.techempower.com/benchmarks/#section=data-r13&hw=ph&test=json
>
> anyone know why vibe.d is shown as "Did not complete" in all tests?

So I have investigated it and find out the reason is probably some memory leak. It is impossible to run vibed test. Every time it is killed by oom killer or there is a exception about unable to allocate memory. But when I enable VibeManualMemoryManagement version it works ok (2GB+ -> 600MB)