On 7/7/2017 12:38 PM, Steven Schveighoffer wrote:
Which would mean that the lack of alloca prototype on Windows is a straight up
bug (the fact that you can just add the declaration and it works is pretty good
proof).
It's in core.stdc.stdlib
On 7/7/2017 12:36 PM, Steven Schveighoffer wrote:
I thought alloca was an intrinsic? Which means that the compiler generates
inline code to add to the stack.
I would think it has to do this, since actually calling a function would
generate a new stack frame.
Yes and yes.
On 7/5/2017 4:48 PM, H. S. Teoh via Digitalmars-d-announce wrote:
In particular, it doesn't seem to do code hoisting, as least
not for this case,
It does not in this case because:
data[0]
is actually:
*data.ptr
i.e. a read through a pointer. Inside the loop, there is also:
data[
On 7/4/2017 2:25 PM, Stefan Koch wrote:
I am not sure how much of this really lends itself to be applied on arm.
The code generator started out as 16 bits, and was that way for 10 years or so.
x87 got added in later. Then it was adapted for 32 bits. Another 10 years went
by, then 64 bits, and
On 7/4/2017 4:09 PM, Johan Engelen wrote:
On Tuesday, 4 July 2017 at 21:10:45 UTC, Walter Bright wrote:
The backend has also been accused of not doing data flow analysis. It does as
good a flow analysis as any compiler.
Please...
DMD: https://goo.gl/wHTPzz
GDC & LDC: https://godbolt.o
On 7/4/2017 2:25 PM, Stefan Koch wrote:
At a first glance it looks highly x86 specific.
The algorithm is not. The details are, of course, since if you read the Intel
CPU manual there is an incredible amount of detail.
I am not sure how much of this really lends itself to be applied on arm.
On 7/4/2017 4:14 PM, H. S. Teoh via Digitalmars-d-announce wrote:
Also, loop unrolling is only the beginning. Other loop optimizations
are just as important, like strength reduction, hoisting, etc.. (Caveat:
I haven't checked whether DMD specifically performs these optimizations.
It does.
Bu
On 7/4/2017 1:15 PM, Stefan Koch wrote:
Most arm implementation are not as forgiving as contemporary x86 processors when
it comes to bad register scheduling and the like.
The backend's scheduler is actually very effective. It mattered with the Pentium
and Pentium Pro processors, but not anymor
On 6/28/2017 7:09 PM, Dsby wrote:
On Thursday, 29 June 2017 at 01:44:10 UTC, Walter Bright wrote:
On 6/27/2017 12:51 AM, Dsby wrote:
what about DIP1000? Is it default?
No.
When will it be default? 2.076 or 2.077?
I don't know at the moment. Currently, Phobos doesn't compile
On 6/28/2017 7:02 PM, H. S. Teoh via Digitalmars-d-announce wrote:
I've been seeing occasional linker errors when compiling with -dip1000
that go away when I drop -dip1000. However, I haven't had the time to
reduce the code sufficiently to file a bug. Is this a known issue, or
should I schedule
On 6/27/2017 12:51 AM, Dsby wrote:
what about DIP1000? Is it default?
No.
https://www.reddit.com/r/programming/comments/6fz3yh/cnow_2017_competitive_advantage_with_d/
Thanks for taking care of this.
On 6/5/2017 10:54 AM, Jon Degenhardt wrote:
On Monday, 5 June 2017 at 14:23:34 UTC, Mike Parker wrote:
The crowd-edited (?) blog post exploring some of D's compile-time features is
now live. Thanks again to everyone who helped out with it.
The blog:
https://dlang.org/blog/2017/06/05/compile-ti
On 6/3/2017 5:20 PM, Mike Parker wrote:
On Saturday, 3 June 2017 at 20:06:05 UTC, Walter Bright wrote:
On 6/3/2017 12:28 AM, Petar Kirov [ZombineDev] wrote:
Personally, making contracts less verbose and more powerful is much higher on
my list
We did discuss bouncing the DIP back with a request
On 6/2/2017 7:17 AM, Mike Parker wrote:
https://github.com/dlang/DIPs/blob/master/DIPs/DIP1003.md
https://github.com/dlang/dmd/pull/6855
On 6/3/2017 12:28 AM, Petar Kirov [ZombineDev] wrote:
Personally, making contracts less verbose and more powerful is much higher on my
list
We did discuss bouncing the DIP back with a request to revamp it as a complete
overhaul of the contract syntax, but decided that this DIP was about resolvi
On 6/2/2017 9:56 PM, MysticZach wrote:
Also Mike Parker seems to be doing a very good job in his appointed position as
DIP manager.
Yes, I am very happy with Mike's contributions on this, as well as on his blog
work. We are very fortunate to have Mike with us.
On 5/30/2017 5:12 AM, Nicholas Wilson wrote:
Ah, isn't English wonderful. I guess Walter is suffering the inverse of the
Calvin & Hobbes "Verbing nouns weirds the language", nouning verbs does weird
the language, but only to those who aren't used to that particular nouning of
the verb.
Just t
On 5/29/2017 6:10 PM, Nicholas Wilson wrote:
there are also GitHub topics [1] which I will also properly fill out. I just
done a pass over the README.md
[1]: https://github.com/blog/2309-introducing-topics
Good. Making the content google-friendly is also extremely important. Back in
the earl
On 5/29/2017 3:52 PM, Nicholas Wilson wrote:
How about calling it D-GPU ? I bet you'd get a lot more clicks on a name like
that.
Thanks, I called it dcompute because naming things is right up there with cache
invalidation.
Calling it D-GPU would be misleading because there should be no reason
On 5/29/2017 2:33 AM, Nicholas Wilson wrote:
Hi all,
I'm happy to announce that the dcompute modifications to LDC are now in the
master branch of LDC. The dcompute extensions require LLVM 3.9.1 or greater for
NVPTX/CUDA and my fork[1] of LLVM for SPIRV.
Someone (sorry I've forgotten who!) at
On 5/24/2017 3:56 PM, Jon Degenhardt wrote:
Its not easy writing an article that doesn't draw some form of criticism. FWIW,
the reason I gave a Python example is because it is very commonly used for this
type of problem and the language is well suited to it. A second reason is that
I've seen se
It's now #4 on the front page of Hacker News:
https://news.ycombinator.com/news
Saved everyone a click to figure out what the DIP is about :-)
https://opensource.com/article/17/5/d-open-source-software-development
http://nwcpp.org
May 17th, 2017 at 7:00 PM
Steptoe Room, Cafeteria 40,
Microsoft Campus,
156th Ave NE,
Redmond, WA 98052.
Eric's talks are generally not to be missed.
We often go out for beer afterwards :-)
On 5/16/2017 8:24 AM, Walter Bright wrote:
Look under the [new] tab. It appeared at about 8:00AM PST.
and reddit:
https://www.reddit.com/r/programming/comments/6bhnss/andrei_alexandrescu_design_by_introspection_talk/
On 5/16/2017 8:25 AM, Adam D. Ruppe wrote:
It's also possible to use underlining.
Yeah, on some systems, but not really on Windows or even all linux terminals.
Color has broader support, though you do want to be careful not to *depend* on
color either.
I've never met an ASCII console that did
On 5/16/2017 8:13 AM, H. S. Teoh via Digitalmars-d-announce wrote:
Simpler solution: print the identifier in quotes, e.g.:
error: undefined identifier 'maybe'
There: instantly clear without needing any colors.
I know about the quotes. With longer message lines, they get lost.
To turn of
Look under the [new] tab. It appeared at about 8:00AM PST.
On 5/16/2017 7:17 AM, Adam D. Ruppe wrote:
So again it is NOT color that bothers me. It is OVERUSE of color for stuff that
isn't important to read the message which dilutes the meaning of color. It isn't
special anymore.
Perhaps. I know I have some trouble distinguishing code from explanatory t
On 5/16/2017 7:00 AM, Andrei Alexandrescu wrote:
Same material as my DConf talk, better delivery. Longer, too, however. -- Andrei
I.e. the Director's Cut.
On 5/16/2017 1:07 AM, Ali Çehreli wrote:
Color is informative to humans, so I'm all for it. I agree with others that it
may be hard to please everyone. Is it possible to use the default scheme of the
terminal?
With all the complaints about color, note that dmd already has been using color
in e
On 5/15/2017 8:35 AM, Adam D. Ruppe wrote:
On Monday, 15 May 2017 at 14:18:30 UTC, Walter Bright wrote:
I eventually want to make the console color package into a generic module, it
could improve a number of console apps.
FYI we already have a few D modules that do console color (among other
On 5/15/2017 3:51 AM, Jonathan M Davis via Digitalmars-d-announce wrote:
Liran was telling me last year about how the folks at Weka had used this to
speed up the stuff in core.time and std.datetime in their local branch and
wanted me to look into updating the official implementation to use it
(un
On 5/15/2017 6:10 AM, Adam D. Ruppe wrote:
Suppose I, or someone else, were to write a PR eliminating your syntax
highlighting in favor of semantic highlighting - colorizing to add more detail
about the error message instead of about the lexer's output. Will you accept it?
I'm glad this sparks
On 5/15/2017 1:05 AM, Jonathan M Davis via Digitalmars-d-announce wrote:
I haven't gotten the chance to look at the dmd error messages yet to see how
they look,
They're a little garish at the moment, but that's just to make sure it's working
correctly. I expect to tune it a bit, especially onc
On 5/14/2017 7:44 PM, ketmar wrote:
sorry for being rude,
Then please do not post rude comments. We expect professional decorum here.
On 5/14/2017 9:04 AM, Andre Pany wrote:
Thanks a lot. In my opinion these kind of changes are small but have huge impact
on the acceptance of a language.
I agree. A couple other improvements needed for error messages:
1. print out the offending line
2. have a clickable link to a more exhausti
On 5/14/2017 3:39 AM, Tomer Filiba wrote:
https://code.dlang.org/packages/divide
Libdivide (http://libdivide.com/) allows converting the DIV instruction (in
runtime) to a series of shifts and MULs, which is much more efficient in
execution time. It works by taking a number (the divisor or "denom
https://github.com/dlang/dmd/pull/6777
It turned out to be unexpectedly easy to implement.
The only downside is now we have to rather tediously tweak the error message
texts so they use backticks.
https://www.reddit.com/r/programming/comments/6aevd6/a_look_into_the_new_ctfe_engine_stefan_koch/
http://dconf.org/2017/index.html
This was a huge success, from the full house, to the great talks, the
cameraderie, and to the tsunami of Pull Requests that resulted from Sunday's
hackathon!
(Definitely the post-conference hackathon will become a standard part of the
schedule!)
I hope ever
On 4/23/2017 5:04 AM, Guillaume Piolat wrote:
The rules of leak-free, exception-safe C++11 aren't so hard.
- single-owneship for everything, invent fake owner if needed
- std::unique_ptr for owning pointer, raw pointers for borrowed
(unique_ptr neatly avoids to write a RAII wrapper for everythi
On 4/11/2017 8:10 AM, Guillaume Piolat wrote:
Newer C++ almost erased leaks and memory errors if you follow it.
C and C++ don't have memory leaks if you are careful. The trouble is, there's no
checking.
On 4/21/2017 10:59 PM, Nicholas Wilson wrote:
As a speaker was I supposed to be sent confirmation of ticket separate to that
of my acceptance as a speaker? 'Cos i didn't receive one.
As a speaker, you're automatically registered. Just show up!
The kiosk closes Sunday Apr 23 at midnight. If you're on the fence, get them
now!
http://dconf.org/2017/registration.html
On 4/10/2017 4:56 PM, Ivan Kazmenko wrote:
I noticed that the backend license in this release (at least the Windows .7z
version) is still the same, as well as the license.txt file at its root. Is it
that there was simply not enough time to reflect the recent changes? And after
the changes are i
On 4/8/2017 6:16 AM, Martin Nowak wrote:
First release candidate for 2.074.0.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.074.0.html
Please report any bugs at https://issues.dlang.org
-Martin
It needs to have the open source backend license merged in!
On 4/10/2017 11:02 AM, Walter Bright wrote:
http://www.infoworld.com/article/3188427/application-development/free-at-last-d-languages-official-compiler-is-open-source.html
I see Andrei already posted this. Oops!
http://www.infoworld.com/article/3188427/application-development/free-at-last-d-languages-official-compiler-is-open-source.html
https://www.heise.de/newsticker/meldung/Programmiersprache-D-Referenzcompiler-DMD-unter-freier-Lizenz-3678894.html
Google translation:
https://translate.google.com/translate?sl=de&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=https%3A%2F%2Fwww.heise.de%2Fnewsticker%2Fmeldung%2FProgrammiersprache-D-Referen
On 4/7/2017 8:14 AM, Walter Bright wrote:
https://github.com/dlang/dmd/pull/6680
Yes, this is for real! Symantec has given their permission to relicense it.
Thank you, Symantec!
While it's still easy to find, for future reference:
https://news.ycombinator.com/item?id=14060846
On 4/9/2017 12:05 PM, Steven Schveighoffer wrote:
As a compiler-writer no-nothing, does this have any implications on the various
back-ends gaining ideas/code from each other? That is, is it possible we see LDC
compile times go down, or DMD optimizations get better?
You can't change the license
On 4/8/2017 10:18 PM, jollie wrote:
Will this change in licensing pave the way for the conversion of
the backend to from c++ to d?
That was going to happen anyway, but it makes it more worthwhile.
On 4/8/2017 4:24 PM, Jethro wrote:
Does this mean that we can now embed the D compiler in to a commercial D app to
be used as a scripting like engine(D app compiles D code then dynamically links
in code while running)?
Yes.
On 4/8/2017 12:07 PM, Martin Tschierschke wrote:
May be we can talk about pr strategy for D in general at Dconf.
I expect that how to best take advantage of this development will be a hot topic
at DConf.
On 4/8/2017 10:16 AM, Iain Buclaw via Digitalmars-d-announce wrote:
To make sure you have your history correct. GDC wrote the work-alike
x86 assembler, and later dual-licensed it to share with LDC. A little
while later I dropped it from GDC as it was not really fit for
purpose, and rather outsi
On 4/8/2017 1:33 AM, Nick Sabalausky (Abscissa) wrote:
AFAIK, Symantec were under no particular obligation here, but none-the-less
chose the consumer/developer-friendly route, and I for one couldn't be more
appreciative. I'm one who can be very critical of, well, everything, but the
fine folks at
On 4/8/2017 1:36 AM, Iain Buclaw via Digitalmars-d-announce wrote:
On 7 April 2017 at 23:49, Walter Bright via Digitalmars-d-announce
wrote:
Note that this also resolves the long-standing legal issue with D's inline
assembler being backend licensed, and so not portable to gdc/ldc.
On 4/8/2017 1:19 AM, Nick Sabalausky (Abscissa) wrote:
Anyone "in the know" have a any "inside scoop" regarding the such organization's
perspective on the "zlib/libpng" license? I tend to favor it for my own OSS
projects, since it's (in my perspective) at least as liberal as Boost, but very,
very
Now #1 on r/programming subreddit!
On 4/7/2017 3:57 PM, Jack Stouffer wrote:
You've said that you've avoided ever looking at other compiler's code to avoid
legal trouble. Is that problem gone now?
No, unless the other compiler is Boost as well.
On 4/7/2017 3:22 PM, David Nadlinger wrote:
Just to clarify for people not usually frequenting these circles: LDC does
support DMD-style inline assembly, but we use a different implementation.
Thanks for pointing that out, I didn't know that. I just assumed LDC would have
gone with a clang-st
On 4/7/2017 2:54 PM, Joseph Rushton Wakeling wrote:
My question should have been more specific: will we see the patch changing the
license in the source code applied to existing stable release branches?
I'd really appreciate it if we could get such a patch applied at least to the
current stable
On 4/7/2017 1:28 PM, Ulrich Küttler wrote:
With all those forks of dmd now well underway, can I please reserve the name
'dork'? ;)
HAHAHAHAHHAHAHAHAHAHAH!
(Hey, I'm feeling pretty good today!)
On 4/7/2017 12:02 PM, Radu wrote:
Also, big up for the whole community as there is a big positive vibe around the
news and nobody is complaining about basic stuff missing line website, docs,
infrastructure etc.
Yes, it's the most positive response to us I've ever seen on HN, by far.
Note that this also resolves the long-standing legal issue with D's inline
assembler being backend licensed, and so not portable to gdc/ldc.
On 4/7/2017 2:04 PM, Jesse Phillips wrote:
MIT almost equal though.
I suspect that the reason MIT came up with their own license is so they could
call it the "MIT License". Branding, ya know.
On 4/7/2017 1:02 PM, Jack Stouffer wrote:
AFAIK the reasons it was chosen were
1. It's as close to public domain as you can get in international law
Yes.
2. It's on all of the "Accepted OSS Licenses" lists that major corps have
because of Boost itself being used in those companies. If your l
On 4/7/2017 9:10 AM, Andrei Alexandrescu wrote:
On 04/07/2017 12:01 PM, Jack Stouffer wrote:
Reddit:
https://www.reddit.com/r/programming/comments/6419py/the_official_d_compiler_is_now_free_as_in_freedom/
Thanks, someone also put it on hackernews - found it by browsing for "new"
threads. -- An
On 4/7/2017 9:15 AM, Basile B. wrote:
Does this apply from now or can the previous DMD releases also be considered as
100% Boost licensed ?
All of it!
On 4/7/2017 8:25 AM, Joseph Rushton Wakeling wrote:
Question: will this 'fix' be backported to existing stable releases? Or will it
just apply going forward?
I ask because it could make a difference to what is legally possible to package
for e.g. Linux distros, etc.
It applies to all of it!
https://github.com/dlang/dmd/pull/6680
Yes, this is for real! Symantec has given their permission to relicense it.
Thank you, Symantec!
On 3/2/2017 6:44 AM, Steven Schveighoffer wrote:
The bus terminal had machines that allowed you to buy the ticket with cash or
credit card I believe, and the same machines validate your ticket as well.
Last year I used those machines to buy a 3 day pass to the transit system, I
think it was lo
On 3/2/2017 1:33 AM, Chris wrote:
On Thursday, 2 March 2017 at 02:24:50 UTC, Walter Bright wrote:
http://www.ibis.com/gb/hotel-5694-ibis-berlin-neukoelln/index.shtml
Last year, some people booked late and it was full and they had to stay at
another hotel.
Maybe someone could post a
On 3/1/2017 6:49 PM, Nicholas Wilson wrote:
Any idea when the speaker list will be published?
I hope soon.
http://www.ibis.com/gb/hotel-5694-ibis-berlin-neukoelln/index.shtml
Last year, some people booked late and it was full and they had to stay at
another hotel.
On 2/27/2017 3:09 AM, Dentcho Bankov wrote:
So I'm in the same boat (paid with PayPal and got 404 on 13-Feb-2017). Is there
a chance I could get a ticket (or some confirmation)?
I had sent a confirmation email. Unfortunately, there are often problems with
this, as the emails get put in the rec
On 2/26/2017 10:03 AM, Petar Kirov [ZombineDev] wrote:
On Saturday, 25 February 2017 at 07:02:48 UTC, Walter Bright wrote:
http://dconf.org/2017/registration.html
Don't forget, it goes up to $400 after Monday.
Hello, I just tried to purchase a ticket, however I got a 'sales ended&#
On 2/25/2017 7:08 PM, Adam Wilson wrote:
On 2/24/17 11:02 PM, Walter Bright wrote:
http://dconf.org/2017/registration.html
Don't forget, it goes up to $400 after Monday.
What do we do if we purchased three pass via EventBrite? I didn't see anywhere
to set name/company info...
On 2/25/2017 5:25 AM, Moritz Maxeiner wrote:
Just registered and was returned to http://dconf.org/2017/thankyou.html
afterwards, which yields a 404 error. Not sure if I should laugh or cry.
Your registration is confirmed. See you there!
http://dconf.org/2017/registration.html
Don't forget, it goes up to $400 after Monday.
On 2/23/2017 10:54 AM, Steven Schveighoffer wrote:
On 2/22/17 6:24 PM, Walter Bright wrote:
Feb 28 is coming up fast!
Website says 2/26. Which is correct?
-Steve
Probably 2/26. It's better to not procrastinate anyway.
Thanks, Mike!
Feb 28 is coming up fast!
On 2/14/2017 2:11 PM, Jonathan M Davis via Digitalmars-d-announce wrote:
LOL. I booked my flight and hotel back in December, and my flight was for
Sunday. Fortunately, after seeing this, I was able to change it, even if it
wasn't free (though the flight was actually cheaper on Monday, so that too
I'll be there. Looking forward to it!
I am happy to announce that there will be a special addition to this year's
DConf.
The conference will not end after the three days of talks but continue on
into Sunday for a hackathon during which people can collaboratively focus on
long-lasting problems and pain points in the D ecosy
On 2/14/2017 6:08 AM, Nicholas Wilson wrote:
Mind there won't
any "convenient" flights any, yay long flights and 7 hours of jet lag.
Convenience is definitely relative :-)
Interestingly, the older I get, the less jet lag bothers me.
I just got mine booked, and noticed the more convenient flights were nearly
full.
On 1/12/2017 2:08 AM, Chris wrote:
On Wednesday, 11 January 2017 at 19:26:06 UTC, Walter Bright wrote:
On 1/11/2017 2:09 AM, Chris wrote:
On Sunday, 8 January 2017 at 22:54:58 UTC, Walter Bright wrote:
Yes. I can't because anything I post gets autobanned.
Why is that?
Probably beca
On 2/9/2017 1:45 PM, Jon Degenhardt wrote:
However, when a PR
associated with the issue is created, the ticket itself is normally not updated
until after the review is finished and the PR closed, to late to help out.
It normally is. I do it for all mine and for others I notice that have not so.
On 2/9/2017 1:06 PM, Joseph Rushton Wakeling wrote:
On Thursday, 9 February 2017 at 20:43:00 UTC, Walter Bright wrote:
*Anyone* in this community can step up and do that.
Anyone can make observations and proposals, but not everyone has the authority
to effect change.
Anyone can proactively
On 2/9/2017 12:29 PM, Joseph Rushton Wakeling wrote:
Yes, but it could be good to examine what can be done to more pro-actively look
at open PRs that have had no recent follow-up.
*Anyone* in this community can step up and do that.
On 2/9/2017 8:55 AM, Joseph Rushton Wakeling wrote:
On Thursday, 9 February 2017 at 09:49:53 UTC, Walter Bright wrote:
In any case, shouldn't it be an uphill battle to merge things? There are a lot
of things that need to be satisfied to merge something. Being too hasty leads
to legacy code
On 2/9/2017 8:48 AM, Joseph Rushton Wakeling wrote:
Contrast this with the experience I had the one time I submitted a (tiny,
trivial) patch to rust: immediately after submitting the PR I got a message from
their 'highfive' robot that included:
* a friendly thank you for the PR;
* the GitHu
On 2/8/2017 11:09 PM, Nick Sabalausky wrote:
And any PRs I have managed to get through were all uphill battles the whole way.
You have contributed 5 PRs to dmd:
https://github.com/dlang/dmd/pulls?q=is%3Apr+author%3Aabscissa
1 is open (it's controversial)
1 closed (today by me)
On 2/8/2017 11:09 PM, Nick Sabalausky wrote:
I fixed an issue where "///"-style doc comments resulted in excessive paragraph
breaks...must've been over a year ago. Simple fix for a nagging bug. The fix
worked. Caused no problems. No controversy. And to this day, just went
completely ignored despi
601 - 700 of 2708 matches
Mail list logo
