[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 --- Comment #9 from timon.g...@gmx.ch --- (In reply to timon.gehr from comment #8) > (In reply to RazvanN from comment #1) > > Issuing an error is the correct behavior. As you can see in the grammar > > [1], > > *(x)++ is parsed the following way:

[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 --- Comment #8 from timon.g...@gmx.ch --- (In reply to RazvanN from comment #1) > Issuing an error is the correct behavior. As you can see in the grammar [1], > *(x)++ is parsed the following way: *UnaryExpression. If a parenthesis is > encountered,

[Issue 17935] [scope] auto-generated destructor not scope aware

https://issues.dlang.org/show_bug.cgi?id=17935 --- Comment #1 from Walter Bright --- https://github.com/dlang/dmd/pull/7283 --

[Issue 17965] Unexplained usage of the FPU while function result already in right XMM registers

https://issues.dlang.org/show_bug.cgi?id=17965 --- Comment #3 from ponce --- @Basile: I also find that unsettling. --

[Issue 17961] std.uni does not compile with -unittest -dip1000

https://issues.dlang.org/show_bug.cgi?id=17961 Jonathan M Davis changed: What|Removed |Added CC|

[Issue 17961] std.uni does not compile with -unittest -dip1000

https://issues.dlang.org/show_bug.cgi?id=17961 --- Comment #5 from hst...@quickfur.ath.cx --- Yeah, I know Phobos is not -dip1000 ready yet. That's probably how this PR got pulled in spite of the breakage. :-P It would be nice to fix these breakages, though. Less trouble for when we do want to

[Issue 17965] Unexplained usage of the FPU while function result already in right XMM registers

https://issues.dlang.org/show_bug.cgi?id=17965 b2.t...@gmx.com changed: What|Removed |Added Keywords||wrong-code --- Comment #2 from

[Issue 17965] Unexplained usage of the FPU while function result already in right XMM registers

https://issues.dlang.org/show_bug.cgi?id=17965 ponce changed: What|Removed |Added CC||alil...@gmail.com --- Comment #1

[Issue 17823] Declaration of a __vector leads to a segfault on OSX 32bits

https://issues.dlang.org/show_bug.cgi?id=17823 b2.t...@gmx.com changed: What|Removed |Added Severity|blocker |normal --

[Issue 17792] [ICE] Internal error: ddmd/backend/el.c 3033 with simd.double4

https://issues.dlang.org/show_bug.cgi?id=17792 --- Comment #1 from b2.t...@gmx.com --- w/ double2 as well (now that double4 usage is restricted by an option) --

[Issue 17419] add __traits(getLinkage, s) to the the linkage of symbol s

https://issues.dlang.org/show_bug.cgi?id=17419 b2.t...@gmx.com changed: What|Removed |Added CC||b2.t...@gmx.com --- Comment #10 from

[Issue 17150] Add a trait to detect the linkage attribute of classes and interfaces

https://issues.dlang.org/show_bug.cgi?id=17150 b2.t...@gmx.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 17893] [REG 2.076.1] contract in templatized final class require nothrow

https://issues.dlang.org/show_bug.cgi?id=17893 b2.t...@gmx.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Issue 17965] New: Unexplained usage of the FPU while function result already in right XMM registers

https://issues.dlang.org/show_bug.cgi?id=17965 Issue ID: 17965 Summary: Unexplained usage of the FPU while function result already in right XMM registers Product: D Version: D2 Hardware: x86_64 OS: All

[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 --- Comment #7 from Simen Kjaeraas --- Unsurprisingly, the function call variant is somewhat unfixable. (T)(a+b) is a very common cast in C, and looks a lot like a function call where T is a function. Even (T)(1,2,3) is valid

[Issue 17964] New: [CTFE] If array is large enough it hits __simd at CTFE

https://issues.dlang.org/show_bug.cgi?id=17964 Issue ID: 17964 Summary: [CTFE] If array is large enough it hits __simd at CTFE Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression

[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 --- Comment #6 from Simen Kjaeraas --- You're at least partly right, though (a[b]).c does work. The smallest example of this bug is probably this: unittest { (a)++; } That should of course fail to compile as well, but

[Issue 17963] New: Spec is incorrect about what is considered a COM interface

https://issues.dlang.org/show_bug.cgi?id=17963 Issue ID: 17963 Summary: Spec is incorrect about what is considered a COM interface Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW

[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 --- Comment #5 from anonymous4 --- Ah, so the problem is that in expression (a[b]).c it's undecidable if the braced expression should be parsed as type or value. --

[Issue 17596] dmd d 2.073.2 and 2.074.1 interim generated dmd segfaults on FreeBSD 12-CURRENT

https://issues.dlang.org/show_bug.cgi?id=17596 --- Comment #17 from anonymous4 --- (In reply to Vladimir Panteleev from comment #4) > dmd/src/root/file.d is now located at dmd/src/ddmd/root/file.d: > > https://github.com/dlang/dmd/blob/master/src/ddmd/root/file.d#L97

[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 --- Comment #4 from RazvanN --- (In reply to Simen Kjaeraas from comment #3) > (In reply to RazvanN from comment #1) > > The behavior is according to the spec, so I will close this as invalid. > > It's perfectly possible

[Issue 17915] [REG 2.073] core.exception.AssertError@ddmd/optimize.d(614): Assertion failure

https://issues.dlang.org/show_bug.cgi?id=17915 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/dd2fcfa3278dda8d5d1109365ef53f7c92dd1276 fix Issue 17915 - [REG 2.073]

[Issue 17955] compiler segfault in DsymbolSemanticVisitor::visit(UnittestDeclaration*)

https://issues.dlang.org/show_bug.cgi?id=17955 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/a32b62f9415c65df9186037fbfe2f9acc1f5be56 fix Issue 17955 - compiler segfault in

[Issue 17915] [REG 2.073] core.exception.AssertError@ddmd/optimize.d(614): Assertion failure

https://issues.dlang.org/show_bug.cgi?id=17915 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17955] compiler segfault in DsymbolSemanticVisitor::visit(UnittestDeclaration*)

https://issues.dlang.org/show_bug.cgi?id=17955 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 7184] parse error on *(x)++

https://issues.dlang.org/show_bug.cgi?id=7184 Simen Kjaeraas changed: What|Removed |Added Keywords||spec

[Issue 17961] std.uni does not compile with -unittest -dip1000

https://issues.dlang.org/show_bug.cgi?id=17961 Dmitry Olshansky changed: What|Removed |Added CC|