On Tuesday, 12 July 2016 at 07:01:05 UTC, Paulo Pinto wrote:
Also contrary to what Microsoft tried to push with C++/CX on
WinRT, besides
game developers not many decided to embrace it.
We didn't embrace it at all, we just have no choice but to use it
for a lot of XBoxOne SDK calls. Any
On Tuesday, 12 July 2016 at 03:25:38 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 18:14:11 UTC, Paulo Pinto wrote:
I don't do Android programming, but NDK is actually fairly rich
in comparison to Apple OSes without Objective-C bindings AFAIK.
The problem seems to be more in the
On Monday, 11 July 2016 at 18:14:11 UTC, Paulo Pinto wrote:
Actually NeXTStep drivers were written in Objective-C.
NeXT was a cool concept, but it was sad that they picked such an
annoying language to build it.
They are not alone, as of Android N, Google is making it pretty
clear that if
Garbage collection allows many syntax "liberalizations" that lack of
garbage collection renders either impossible or highly dangerous. (In
this definition of "garbage collection" I'm including variations like
reference counting.) For an example of this consider the dynamic array
type. You
On 2016-07-11 14:23, Luís Marques wrote:
Doesn't seem to work for me on 10.11.5. Maybe you need to enable that on
the latest OSes?
It works for me. I don't recall specifically enabling crash reports. Are
you looking at "All Messages"? You can also look at
~/Library/Logs/DiagnosticReports to
On Monday, 11 July 2016 at 16:44:27 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 16:26:11 UTC, Paulo Pinto wrote:
Happy not to disappoint. :)
You never disappoint in the GC department ;-)
OS vendors are the ones that eventually decided what is a
systems programming language
On Monday, 11 July 2016 at 16:26:11 UTC, Paulo Pinto wrote:
Happy not to disappoint. :)
You never disappoint in the GC department ;-)
OS vendors are the ones that eventually decided what is a
systems programming language on their OSes.
To a large extent on Apple and Microsoft OSes. Not so
On Monday, 11 July 2016 at 14:12:35 UTC, Chris wrote:
You focus on a small niche where people use all kinds of
performance tricks even in C and C++. A lot of software doesn't
care about GC overheads, however, and without GC a lot of
people wouldn't even have considered it.
+1
A large
On Monday, 11 July 2016 at 14:58:16 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 14:45:56 UTC, Paulo Pinto wrote:
The biggest problem with D isn't the GC, is lack of focus to
make it stand out versus .NET Native, Swift, Rust, Ada, SPARK,
Java, C++17.
I knew you would chime
On Monday, 11 July 2016 at 14:45:56 UTC, Paulo Pinto wrote:
The biggest problem with D isn't the GC, is lack of focus to
make it stand out versus .NET Native, Swift, Rust, Ada, SPARK,
Java, C++17.
How true!
That's the only real problem with this beautiful language!
/P
On Monday, 11 July 2016 at 14:12:35 UTC, Chris wrote:
Most certainly from a multi-purpose language. GC would have
been demanded sooner or later. The mistake was not to make it
optional from the beginning.
If D was designed as a high level language then it would be a
mistake not to provide a
On Monday, 11 July 2016 at 14:03:36 UTC, Infiltrator wrote:
On Monday, 11 July 2016 at 13:24:14 UTC, Chris wrote:
...
To have GC was definitely a good decision. What was not so
good was that it was not optional with a simple on/off switch.
...
I know that I'm missing something here, but
On Monday, 11 July 2016 at 14:45:56 UTC, Paulo Pinto wrote:
The biggest problem with D isn't the GC, is lack of focus to
make it stand out versus .NET Native, Swift, Rust, Ada, SPARK,
Java, C++17.
I knew you would chime in... Neither .NET, Swift or Java should
be considered system level
On Monday, 11 July 2016 at 14:02:09 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 13:24:14 UTC, Chris wrote:
I bet you that if D hadn't had GC when it first came out,
people would've mentioned manual memory management as a reason
not to use GC. I never claimed that D was
On Monday, 11 July 2016 at 14:19:07 UTC, ketmar wrote:
On Monday, 11 July 2016 at 14:02:09 UTC, Ola Fosheim Grøstad
wrote:
Actually, I am certain that GC is a feature that _nobody_
would expect from a system level language, outside the
Go-crowd.
hello. i am the man born to ruin your world.
On Monday, 11 July 2016 at 13:56:30 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 12:18:26 UTC, ketmar wrote:
and most of those people never even started to use D. took a
brief look, maybe wrote "helloworld", and that's all. it
Where do you get this from?
from reading this NG
On Monday, 11 July 2016 at 14:02:09 UTC, Ola Fosheim Grøstad
wrote:
Actually, I am certain that GC is a feature that _nobody_ would
expect from a system level language, outside the Go-crowd.
hello. i am the man born to ruin your world.
On Monday, 11 July 2016 at 14:02:09 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 13:24:14 UTC, Chris wrote:
I bet you that if D hadn't had GC when it first came out,
people would've mentioned manual memory management as a reason
not to use GC. I never claimed that D was
On Monday, 11 July 2016 at 13:24:14 UTC, Chris wrote:
...
To have GC was definitely a good decision. What was not so
good was that it was not optional with a simple on/off switch.
...
I know that I'm missing something here, but what's wrong with the
functions provided in core.memory?
On Monday, 11 July 2016 at 13:24:14 UTC, Chris wrote:
I bet you that if D hadn't had GC when it first came out,
people would've mentioned manual memory management as a reason
not to use GC. I never claimed that D was _propelled_ by GC,
but that it was a feature that most users would expect.
On Monday, 11 July 2016 at 12:18:26 UTC, ketmar wrote:
and most of those people never even started to use D. took a
brief look, maybe wrote "helloworld", and that's all. it
Where do you get this from? Quite a few D programmers have gone
to C++ and Rust.
D *can* be used without GC. and it
I bet you that if D hadn't had GC when it first came out,
people would've mentioned manual memory management as a reason
not to use GC. I never claimed that D was _propelled_ by GC,
but that it was a feature that most users would expect. Not
having it would probably have done more harm than
On Monday, 11 July 2016 at 11:59:51 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 09:30:37 UTC, Chris wrote:
Lisp or SmallTalk)[1]. D couldn't have afforded not to have GC
when it first came out. It was expected of a (new) language to
provide GC by then - and GC had become a
On Sunday, 10 July 2016 at 18:53:52 UTC, Jacob Carlborg wrote:
On OS X when an application segfaults a crash report will be
generated. It's available in the Console application.
Doesn't seem to work for me on 10.11.5. Maybe you need to enable
that on the latest OSes? In any case, that will
On Monday, 11 July 2016 at 11:59:51 UTC, Ola Fosheim Grøstad
wrote:
Just go look at what people who gave up on D claim to be a
major reason, the GC scores high...
and most of those people never even started to use D. took a
brief look, maybe wrote "helloworld", and that's all. it doesn't
On Saturday, 9 July 2016 at 08:40:00 UTC, Walter Bright wrote:
On 7/8/2016 2:36 PM, Luís Marques wrote:
On Friday, 8 July 2016 at 21:26:19 UTC, Walter Bright wrote:
Only on Windows, and that's a common source of frustration
for me :(
Linux too.
Not by default, right?
-g
Well, it
On Monday, 11 July 2016 at 08:55:06 UTC, ketmar wrote:
On Monday, 11 July 2016 at 08:45:21 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 08:43:03 UTC, ketmar wrote:
On Monday, 11 July 2016 at 07:16:57 UTC, Ola Fosheim Grøstad
wrote:
There aren't many people you trust then...
On Monday, 11 July 2016 at 09:30:37 UTC, Chris wrote:
Lisp or SmallTalk)[1]. D couldn't have afforded not to have GC
when it first came out. It was expected of a (new) language to
provide GC by then - and GC had become a selling point for new
languages.
This is not true, it is just wishful
On Sunday, 10 July 2016 at 03:25:16 UTC, Ola Fosheim Grøstad
wrote:
Just like there is no C++ book that does not rant about how
great RAII is... What do you expect from a language evangelic?
The first Java implementation Hotspot inherited its technology
from StrongTalk, a Smalltalk
On Monday, 11 July 2016 at 08:45:21 UTC, Ola Fosheim Grøstad
wrote:
On Monday, 11 July 2016 at 08:43:03 UTC, ketmar wrote:
On Monday, 11 July 2016 at 07:16:57 UTC, Ola Fosheim Grøstad
wrote:
There aren't many people you trust then...
exactly. 99% of people are idiots.
100%
it depends of
On Monday, 11 July 2016 at 08:43:03 UTC, ketmar wrote:
On Monday, 11 July 2016 at 07:16:57 UTC, Ola Fosheim Grøstad
wrote:
There aren't many people you trust then...
exactly. 99% of people are idiots.
100%
On Monday, 11 July 2016 at 07:16:57 UTC, Ola Fosheim Grøstad
wrote:
There aren't many people you trust then...
exactly. 99% of people are idiots.
On Sunday, 10 July 2016 at 19:12:46 UTC, ketmar wrote:
then i won't trust a word they said.
There aren't many people you trust then... Seriously, in academic
contexts a statement like «X is a garbage collected language»
always means tracing. It would be very odd to assume that X used
On Sunday, 10 July 2016 at 17:06:20 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 10 July 2016 at 17:03:26 UTC, ketmar wrote:
On Sunday, 10 July 2016 at 16:58:49 UTC, Ola Fosheim Grøstad
wrote:
I've never been to a lecture/presentation where "garbage
collection" did not mean "tracing garbage
On 2016-07-08 19:07, Luís Marques wrote:
I was referring to the stack trace on segfault, but regarding the user
of debuggers on a Mac with D, most of the time it doesn't work very well
for me. I think last time I used lldb (maybe last week) when I tried to
print something in a D program nothing
On Sunday, 10 July 2016 at 17:03:26 UTC, ketmar wrote:
On Sunday, 10 July 2016 at 16:58:49 UTC, Ola Fosheim Grøstad
wrote:
I've never been to a lecture/presentation where "garbage
collection" did not mean "tracing garbage collection".
then you probably watched some... wrong lections. ;-)
On Sunday, 10 July 2016 at 16:58:49 UTC, Ola Fosheim Grøstad
wrote:
I've never been to a lecture/presentation where "garbage
collection" did not mean "tracing garbage collection".
then you probably watched some... wrong lections. ;-)
On Sunday, 10 July 2016 at 09:05:47 UTC, ketmar wrote:
On Sunday, 10 July 2016 at 09:04:25 UTC, Ola Fosheim Grøstad
wrote:
Nothing to do with hipsters. The common interpretation for
«garbage collection» in informal context has always been a
tracing collector. I've never heard anything else in
On Sunday, 10 July 2016 at 09:04:25 UTC, Ola Fosheim Grøstad
wrote:
Nothing to do with hipsters. The common interpretation for
«garbage collection» in informal context has always been a
tracing collector. I've never heard anything else in any
informal CS context.
i always heard that "garbage
On Sunday, 10 July 2016 at 06:19:28 UTC, ketmar wrote:
On Sunday, 10 July 2016 at 02:02:23 UTC, Ola Fosheim Grøstad
wrote:
Reference counting is a technique for collecting garbage, but
the term «garbage collection» is typically used for techniques
that catch cycles by tracing down chains of
On Sunday, 10 July 2016 at 02:02:23 UTC, Ola Fosheim Grøstad
wrote:
Reference counting is a technique for collecting garbage, but
the term «garbage collection» is typically used for techniques
that catch cycles by tracing down chains of pointers:
i don't care about hipsters redefining the
On Sunday, 10 July 2016 at 02:28:58 UTC, Ola Fosheim Grøstad
wrote:
So what D needs is:
1. local garbage collection (for a single fiber or a facade to
a graph).
2. solid global ownership management (for both resources and
memory).
ketmar doesn't need that. even for his real-time audio
On Sunday, 10 July 2016 at 02:08:36 UTC, Ola Fosheim Grøstad
wrote:
No, manual reference counting is not particularly slow.
Automatic reference counting is also not considered to be
slower than GC.
i keep insisting that refcounting IS GC. please, stop call it
something else.
On Saturday, 9 July 2016 at 09:15:19 UTC, Chris wrote:
Yes, of course the "write-once-run-everywhere" fairy tale
helped to spread Java, but while it was gaining traction GC
became a feature everybody wanted. Sorry, but there is not a
single book or introduction to Java that doesn't go on about
On Saturday, 9 July 2016 at 11:27:13 UTC, ketmar wrote:
and with refcounting i have to *explicitly* mark all the code
as "no refcounting here", or accept refcounting overhead for
nothing.
That would be automatic reference counting ;-)... Reference
counting is ok for shared ownership, but in
On Saturday, 9 July 2016 at 11:10:22 UTC, bachmeier wrote:
On Saturday, 9 July 2016 at 08:06:54 UTC, ketmar wrote:
On Saturday, 9 July 2016 at 07:52:57 UTC, Ola Fosheim Grøstad
wrote:
removed the GC
...
replaced it with automatic reference counting.
you *do* know that refcounting *is* GC,
On Saturday, 9 July 2016 at 08:06:54 UTC, ketmar wrote:
On Saturday, 9 July 2016 at 07:52:57 UTC, Ola Fosheim Grøstad
wrote:
removed the GC
...
replaced it with automatic reference counting.
you *do* know that refcounting *is* GC, do you? ;-)
Reference counting is a technique for
On Saturday, 9 July 2016 at 11:10:22 UTC, bachmeier wrote:
On Saturday, 9 July 2016 at 08:06:54 UTC, ketmar wrote:
On Saturday, 9 July 2016 at 07:52:57 UTC, Ola Fosheim Grøstad
wrote:
removed the GC
...
replaced it with automatic reference counting.
you *do* know that refcounting *is* GC,
On Saturday, 9 July 2016 at 11:10:22 UTC, bachmeier wrote:
p.s. also, it is funny that D's GC is actually *better* if one to
avoid GC completely, yet people continue to ask for refcounting.
i meat: if i don't want to use GC in D, it is as easy as avoid
`new` (and delegates with closures). any
On Saturday, 9 July 2016 at 11:10:22 UTC, bachmeier wrote:
The objection was always that it would make the code run more
slowly.
i tend to ignore such persons completely after such a claim: they
are obviously incompetent as programmers.
i also tend to ignore whole "@nogc" movement: it is
On Saturday, 9 July 2016 at 08:06:54 UTC, ketmar wrote:
On Saturday, 9 July 2016 at 07:52:57 UTC, Ola Fosheim Grøstad
wrote:
removed the GC
...
replaced it with automatic reference counting.
you *do* know that refcounting *is* GC, do you? ;-)
And that's a very important point, because the
On Saturday, 9 July 2016 at 07:52:57 UTC, Ola Fosheim Grøstad
wrote:
On Friday, 8 July 2016 at 22:25:37 UTC, Chris wrote:
after Java. And D was invented when GC was expected by many
people.
The GC was by far the most criticised feature of D...
GC was a big selling point. Every Java book
On 7/8/2016 2:36 PM, Luís Marques wrote:
On Friday, 8 July 2016 at 21:26:19 UTC, Walter Bright wrote:
Only on Windows, and that's a common source of frustration for me :(
Linux too.
Not by default, right?
-g
On Saturday, 9 July 2016 at 07:52:57 UTC, Ola Fosheim Grøstad
wrote:
removed the GC
...
replaced it with automatic reference counting.
you *do* know that refcounting *is* GC, do you? ;-)
On Friday, 8 July 2016 at 22:25:37 UTC, Chris wrote:
after Java. And D was invented when GC was expected by many
people.
The GC was by far the most criticised feature of D...
GC was a big selling point. Every Java book went on about how
Err... no, the big selling point that gave Java
On Friday, 8 July 2016 at 21:53:58 UTC, Ola Fosheim Grøstad wrote:
On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote:
As for GC, it's hard to tell. When D was actually (not
hypothetically) created, GC was _the_ big thing. Java had just
taken off, people were pissed off with C/C++,
On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote:
As for GC, it's hard to tell. When D was actually (not
hypothetically) created, GC was _the_ big thing. Java had just
taken off, people were pissed off with C/C++, programming and
coding was becoming more and more common.
Errr... Garbage
On Friday, 8 July 2016 at 21:26:19 UTC, Walter Bright wrote:
Only on Windows, and that's a common source of frustration for
me :(
Linux too.
Not by default, right? Only with the magic import and call.
That's certainly better than on OS X, where there's no segfault
handler at all (I don't
On 7/8/2016 8:17 AM, Luís Marques wrote:
On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote:
If the program is compiled with -g and it crashes (seg faults) you'll usually
at least get a stack trace. Running it under a debugger will get you much more
information.
Only on Windows, and
p.s. it's not something specifical to D. any program that
"catches" segfault by itself should be burnt with fire.
On Friday, 8 July 2016 at 17:04:04 UTC, Luís Marques wrote:
On Friday, 8 July 2016 at 15:31:53 UTC, ketmar wrote:
core.exception.AssertError@z00.d(2): BOOM!
what am i doing wrong? O_O
That's an exception, not a segfault.
Try something like int* x; *x = 42;
segfault is
On Friday, 8 July 2016 at 16:08:42 UTC, bachmeier wrote:
Yep. If you're going to pick any feature to use to sell a new
language, lack of GC is the worst. The only ones that care (and
it's a small percentage) are the ones that are least likely to
switch due to their existing tools, libraries,
On Friday, 8 July 2016 at 15:30:12 UTC, Schrom, Brian T wrote:
I've had reasonable success using lldb on mac.
I was referring to the stack trace on segfault, but regarding the
user of debuggers on a Mac with D, most of the time it doesn't
work very well for me. I think last time I used lldb
On Friday, 8 July 2016 at 16:08:42 UTC, bachmeier wrote:
On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote:
As for GC, it's hard to tell. When D was actually (not
hypothetically) created, GC was _the_ big thing. Java had just
taken off, people were pissed off with C/C++, programming and
On Friday, 8 July 2016 at 15:31:53 UTC, ketmar wrote:
core.exception.AssertError@z00.d(2): BOOM!
what am i doing wrong? O_O
That's an exception, not a segfault.
Try something like int* x; *x = 42;
On 7/8/16 8:22 AM, Luís Marques via Digitalmars-d wrote:
> On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote:
>> If the program is compiled with -g and it crashes (seg faults)
>> you'll usually at least get a stack trace. Running it under a
>> debugger will get you much more
On Friday, 8 July 2016 at 12:46:03 UTC, Chris wrote:
As for GC, it's hard to tell. When D was actually (not
hypothetically) created, GC was _the_ big thing. Java had just
taken off, people were pissed off with C/C++, programming and
coding was becoming more and more common. Not having GC
On Friday, 8 July 2016 at 15:17:33 UTC, Luís Marques wrote:
On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote:
If the program is compiled with -g and it crashes (seg faults)
you'll usually at least get a stack trace. Running it under a
debugger will get you much more information.
On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote:
If the program is compiled with -g and it crashes (seg faults)
you'll usually at least get a stack trace. Running it under a
debugger will get you much more information.
Only on Windows, and that's a common source of frustration for
On Friday, 8 July 2016 at 01:17:55 UTC, Luís Marques wrote:
Sometimes I idly wonder what would have happened if D were
available in the 80's. Sort of like if you put a modern car
for sale in the 1960's.
I've also thought about that from time to time. I think D would
have been very
On Wednesday, 6 July 2016 at 04:56:07 UTC, Walter Bright wrote:
It's certainly doable, but in an age of priorities I suspect
the time is better spent on
\o/
improving 64 bit code generation.
/o\
On Sunday, 3 July 2016 at 06:23:05 UTC, Walter Bright wrote:
Thanks for taking the time to write this. Let me see if I can
help.
Wow, this was very well handled. Thanks for keeping your head
cool and answering in a constructive, friendly and informative
manner. It's even more admirable
On 06/07/16 07:01, Walter Bright wrote:
Apple has dropped all 32 bit support
No. For ARM 32bit is still relevant. On OS X the Simulator (used to test
iOS applications) are running the iOS applications as x86 (both 32 and
64bit) even though the iOS deceives are running ARM.
Apparently some
On Wednesday, 6 July 2016 at 10:26:27 UTC, qznc wrote:
If you want to distribute a binary
gods save me! why should i do that? i am GPL fanatic. and if i'm
doing contract work, i know what machines my contractor will have.
for x86 you only have the 386 instructions. Ok, 686 is probably
$subj.
On Wednesday, 6 July 2016 at 04:56:07 UTC, Walter Bright wrote:
It's certainly doable, but in an age of priorities I suspect
the time is better spent on improving 64 bit code generation.
It's not like it is a blocker for anyone, there is:
- assembly
- auto-vectorization
- LDC
Not worth your
On Wednesday, 6 July 2016 at 01:30:46 UTC, ketmar wrote:
and i'm curious why everyone is so amazed by 64-bit systems.
none of my software is using more than 2GB of RAM. why should i
pay for something i don't need? like, all pointers are
magically twice bigger. hello, cache lines, i have a
On 7/5/2016 6:30 PM, ketmar wrote:
I'm curious about why you require 32 bits.
and i'm curious why everyone is so amazed by 64-bit systems. none of my software
is using more than 2GB of RAM. why should i pay for something i don't need?
like, all pointers are magically twice bigger. hello, cache
On 7/5/2016 6:06 PM, deadalnix wrote:
On Tuesday, 5 July 2016 at 23:56:48 UTC, Walter Bright wrote:
On 7/5/2016 2:44 PM, ketmar wrote:
anyway, fixing long-standing bug with `align()` being ignored on stack variables
will allow to use SIMD on x86.
Not really. The alignment requirement has to
p.s. *heat. ;-)
p.p.s. and i can use SIMD with DMD built-in asm, of course.
that's what i did in Follin, and it works like a charm. but, of
course, the code is completely unportable -- and this is
something i wanted to avoid...
On Wednesday, 6 July 2016 at 03:23:18 UTC, Basile B. wrote:
while using a 64 bit linux will help you, dancing naked in the
street won't.
it will really help me to head my house, yes. so you proposing me
to rebuild the world, and all my custom-built software (alot!)
for... for nothing, as (i
On Wednesday, 6 July 2016 at 02:34:04 UTC, ketmar wrote:
On Wednesday, 6 July 2016 at 02:10:09 UTC, Basile B. wrote:
ok, bad bet but why do you insist with DMD 32 bit SIMD support
? can't you use a 64 bit linux distribution ?
i can even dance naked on the street, no problems. but i just
On Wednesday, 6 July 2016 at 02:10:09 UTC, Basile B. wrote:
ok, bad bet but why do you insist with DMD 32 bit SIMD support
? can't you use a 64 bit linux distribution ?
i can even dance naked on the street, no problems. but i just
can't see a reason to do that.
On Wednesday, 6 July 2016 at 01:27:11 UTC, ketmar wrote:
On Tuesday, 5 July 2016 at 23:50:35 UTC, Basile B. wrote:
Major Linux distributions...
...
Are you windows Ketmar ?
no. GNU/Linux here. and i don't care what shitheads from "major
linux distributions" may think.
ok, bad bet but why
On Tuesday, 5 July 2016 at 23:56:48 UTC, Walter Bright wrote:
On 7/5/2016 2:44 PM, ketmar wrote:
anyway, fixing long-standing bug with `align()` being ignored
on stack variables
will allow to use SIMD on x86.
Not really. The alignment requirement has to be done by all
functions, whether
On Tuesday, 5 July 2016 at 23:50:35 UTC, Basile B. wrote:
Major Linux distributions...
...
Are you windows Ketmar ?
no. GNU/Linux here. and i don't care what shitheads from "major
linux distributions" may think.
On Tuesday, 5 July 2016 at 23:56:48 UTC, Walter Bright wrote:
On 7/5/2016 2:44 PM, ketmar wrote:
anyway, fixing long-standing bug with `align()` being ignored
on stack variables
will allow to use SIMD on x86.
Not really. The alignment requirement has to be done by all
functions, whether
On 7/5/2016 2:44 PM, ketmar wrote:
anyway, fixing long-standing bug with `align()` being ignored on stack variables
will allow to use SIMD on x86.
Not really. The alignment requirement has to be done by all functions, whether
they use SIMD or not.
4. people wanting high performance are
On Tuesday, 5 July 2016 at 22:38:29 UTC, Seb wrote:
On Tuesday, 5 July 2016 at 21:44:17 UTC, ketmar wrote:
On Tuesday, 5 July 2016 at 20:27:58 UTC, Walter Bright wrote:
4. people wanting high performance are going to be using 64
bits anyway
so i'm not in a set of "people". ok.
It might be
On Tuesday, 5 July 2016 at 21:44:17 UTC, ketmar wrote:
On Tuesday, 5 July 2016 at 20:27:58 UTC, Walter Bright wrote:
4. people wanting high performance are going to be using 64
bits anyway
so i'm not in a set of "people". ok.
It might be a good time to think about your hardware. Btw there
On Tuesday, 5 July 2016 at 20:27:58 UTC, Walter Bright wrote:
1. so D can run on earlier 32 bit processors without SIMD
this is something programmer should check in runtime if he is
using SIMD.
2. SIMD support requires the stack be aligned everywhere to 128
bits. This can be a bit
On 7/5/2016 9:11 AM, ketmar wrote:
'cause even documentation says so: "The vector extensions are currently
implemented for the OS X 32 bit target, and all 64 bit targets.". and this time
documentation is correct.
This is because:
1. so D can run on earlier 32 bit processors without SIMD
2.
On Sunday, 3 July 2016 at 07:16:17 UTC, Bauss wrote:
On Sunday, 3 July 2016 at 04:37:02 UTC, D is crap wrote:
[...]
Say what? I have used it for multiple big projects of my own
ranging from 4-10 lines of code?
[...]
[...]
That's adorable. You think that's a big project :D
On Tuesday, 5 July 2016 at 14:38:07 UTC, ZombineDev wrote:
The fact core.simd exists (regardless how well it works)
contradicts your statement.
Of course not. "core.simd" has been an excuse for not doing
better.
The floats problem you talk about does not affect SIMD, so to
Of course it
On Tuesday, 5 July 2016 at 14:52:33 UTC, ZombineDev wrote:
On Tuesday, 5 July 2016 at 12:40:57 UTC, ketmar wrote:
On Tuesday, 5 July 2016 at 11:27:33 UTC, ZombineDev wrote:
https://dlang.org/spec/simd.html and the list of intrinsics
core.simd is completely unusable on any 32-bit targets
On Tuesday, 5 July 2016 at 12:40:57 UTC, ketmar wrote:
On Tuesday, 5 July 2016 at 11:27:33 UTC, ZombineDev wrote:
https://dlang.org/spec/simd.html and the list of intrinsics
core.simd is completely unusable on any 32-bit targets except
hipsteros.
Why? I only found this issue:
On Tuesday, 5 July 2016 at 12:59:27 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 5 July 2016 at 11:27:33 UTC, ZombineDev wrote:
Have you put any enhancement request on
https://issues.dlang.org or written a DIP? If not, I can
guarantee with almost 100% that it will not get worked because
no one
On Tuesday, 5 July 2016 at 11:27:33 UTC, ZombineDev wrote:
Have you put any enhancement request on
https://issues.dlang.org or written a DIP? If not, I can
guarantee with almost 100% that it will not get worked because
no one knows what you need.
SIMD support has been discussed and shot down
On Tuesday, 5 July 2016 at 11:27:33 UTC, ZombineDev wrote:
https://dlang.org/spec/simd.html and the list of intrinsics
core.simd is completely unusable on any 32-bit targets except
hipsteros.
On Tuesday, 5 July 2016 at 09:51:01 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 5 July 2016 at 09:23:42 UTC, ZombineDev wrote:
https://gist.github.com/9il/a167e56d7923185f6ce253ee14969b7f
https://gist.github.com/9il/58c1b80110de2db5f2eff6999346a928
available today with LDC ;)
I meant good
1 - 100 of 140 matches
Mail list logo
