http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #14 from Iain Buclaw 2014-02-13 19:57:41
GMT ---
(In reply to comment #11)
> OK. So do you want to fix this or shall I?
I'm pretty tied up getting gdb D into shape, and working with a publishing
company in reviewing a new D2 book, and
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #13 from Iain Buclaw 2014-02-13 19:21:54
GMT ---
(In reply to comment #12)
> Yes, I agree all parameters should be evaluated LTR. In fact LTR is more
> general than that - in an assignment e1 = e2, e1 should be evaluated first.
> Also
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #12 from Andrei Alexandrescu 2014-02-13
18:15:27 GMT ---
Yes, I agree all parameters should be evaluated LTR. In fact LTR is more
general than that - in an assignment e1 = e2, e1 should be evaluated first.
Also in a computed function c
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #11 from Johannes Pfau 2014-02-13 17:25:20
GMT ---
OK. So do you want to fix this or shall I?
--
Configure bugmail: http://bugzilla.gdcproject.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are w
http://bugzilla.gdcproject.org/show_bug.cgi?id=84
--- Comment #6 from Johannes Pfau 2014-02-13 15:01:52
GMT ---
Not into registers might be OK, but if we have code like this:
-
shared int a;
void doSomething()
{
for(int i = 0; i < 10; i++)
atomicStore(a, i);
}
--
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #10 from Iain Buclaw 2014-02-13 08:37:03
GMT ---
(In reply to comment #6)
> Iain, do you want to look into this again?
>
> I read some of the old discussions and the dlang.org pull request and to
> summarize:
> * All functions should
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #9 from Iain Buclaw 2014-02-13 08:30:13
GMT ---
LTR is already enforced for LINKd functions. See d-codegen.cc(d_build_call)
// Evaluate the argument before passing to the function.
// Needed for left to right evaluation.
if (tf->link
http://bugzilla.gdcproject.org/show_bug.cgi?id=84
--- Comment #4 from Iain Buclaw 2014-02-13 08:26:55
GMT ---
I'm pretty persistent on forcing shared variables to not go into registers.
However we need a better system for setting TREE_ADDRESSABLE on the type
without causing GCC backend to panic
http://bugzilla.gdcproject.org/show_bug.cgi?id=84
--- Comment #5 from Iain Buclaw 2014-02-13 08:27:22
GMT ---
(If alternatives is what we should go for)
--
Configure bugmail: http://bugzilla.gdcproject.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are wat
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #8 from Johannes Pfau 2014-02-13 08:23:04
GMT ---
And one more link: DMD bug:
https://d.puremagic.com/issues/show_bug.cgi?id=6620
--
Configure bugmail: http://bugzilla.gdcproject.org/userprefs.cgi?tab=email
--- You are receiving
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #7 from Johannes Pfau 2014-02-13 08:18:34
GMT ---
Another link for reference: Pull request for the spec which demands LTR
evaluation:
https://github.com/D-Programming-Language/dlang.org/pull/6
--
Configure bugmail: http://bugzilla.gd
http://bugzilla.gdcproject.org/show_bug.cgi?id=8
--- Comment #6 from Johannes Pfau 2014-02-13 08:17:33
GMT ---
Iain, do you want to look into this again?
I read some of the old discussions and the dlang.org pull request and to
summarize:
* All functions should be evaluated LTR, even extern(C)
*
http://bugzilla.gdcproject.org/show_bug.cgi?id=10
--- Comment #12 from Johannes Pfau 2014-02-13 08:06:11
GMT ---
I had a look at the other bugs but it's difficult to estimate how much work is
needed for those that qualify as 'more important' (NRVO, non-POD types). NRVO
needs some work/clarificat
http://bugzilla.gdcproject.org/show_bug.cgi?id=93
Johannes Pfau changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
14 matches
Mail list logo
