[Issue 12429] SIMD vector type errors are too eager
https://issues.dlang.org/show_bug.cgi?id=12429 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Walter Bright --- The trouble is that float8 is supported by front ends other than DMD, so putting the error into the front end makes it less generic. DMD not supporting float8 is listed in other bugzilla issues. I've currently begun work on supporting float8 in DMD, so fixing this is not worth the effort. --
[Issue 10447] Refused increment of double2 with a immutable(double2)
https://issues.dlang.org/show_bug.cgi?id=10447 Walter Bright changed: What|Removed |Added Keywords||pull --- Comment #1 from Walter Bright --- https://github.com/dlang/dmd/pull/6272 --
[Issue 13357] [ICE] Segfault on comparison of rvalue __vector and array
https://issues.dlang.org/show_bug.cgi?id=13357 --- Comment #2 from Walter Bright --- At least it doesn't seg fault anymore. --
[Issue 8047] important opcodes missing from core/simd.d
https://issues.dlang.org/show_bug.cgi?id=8047 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Walter Bright --- These have been in core.simd for a while. --
[Issue 5028] Problem with named mixins in base class and derived class
https://issues.dlang.org/show_bug.cgi?id=5028 Xiao Di Guan changed: What|Removed |Added CC||x...@puxlit.net --
[Issue 16681] ICE 1662
https://issues.dlang.org/show_bug.cgi?id=16681 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #2 from Walter Bright --- I'm not sure what to do with this. The code fragment is too incomplete to compile (numerous undefined symbols), and the PR was closed. --
[Issue 16048] std.getopt: duplicated options are not detected
https://issues.dlang.org/show_bug.cgi?id=16048 --- Comment #2 from Andrej Mitrovic --- https://github.com/dlang/phobos/pull/4917 --
[Issue 16048] std.getopt: duplicated options are not detected
https://issues.dlang.org/show_bug.cgi?id=16048 --- Comment #1 from Andrej Mitrovic --- In fact duplicate long options aren't detected either. --
[Issue 16048] std.getopt: duplicated options are not detected
https://issues.dlang.org/show_bug.cgi?id=16048 Andrej Mitrovic changed: What|Removed |Added Summary|std.getopt: duplicated |std.getopt: duplicated |(short) options are not |options are not detected |detected| --
[Issue 16601] No way to configure number of worker threads for default taskPool
https://issues.dlang.org/show_bug.cgi?id=16601 Andrej Mitrovic changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrej Mitrovic --- Oh wait, I believe defaultPoolThreads already does this. --
[Issue 16679] prefetch on old pentium d results in an illegal instruction
https://issues.dlang.org/show_bug.cgi?id=16679 Walter Bright changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Walter Bright --- (In reply to Brad Roberts from comment #4) > Reopened and lowered to major from regression until the cpuid work is done > and the test is re-enabled. I would have suggested waiting for the right > fix rather than the quick fix, but in neither case should we loose track of > the disabled test. This is already covered by https://issues.dlang.org/show_bug.cgi?id=16704 --
[Issue 16381] Wrapping a float4 array leads to segfault.
https://issues.dlang.org/show_bug.cgi?id=16381 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 16381] Wrapping a float4 array leads to segfault.
https://issues.dlang.org/show_bug.cgi?id=16381 --- Comment #10 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/1429da40f6bd24c702eb4a5c0685faa0addfcb39 fix Issue 16381 - Wrapping a float4 array leads to segfault https://github.com/dlang/dmd/commit/2210757dfdcf637022cec835dbbc6cbb5deca73d Merge pull request #6268 from WalterBright/fix16381 fix Issue 16381 - Wrapping a float4 array leads to segfault --
[Issue 16116] Infinite loop on (somewhat complex) simd math
https://issues.dlang.org/show_bug.cgi?id=16116 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 16116] Infinite loop on (somewhat complex) simd math
https://issues.dlang.org/show_bug.cgi?id=16116 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/089cea83dd054f78db9e0145c4bef6d298f165a3 fix Issue 16116 - Infinite loop on (somewhat complex) simd math https://github.com/dlang/dmd/commit/df96ac9695393ccf8139cc7ca5db48edce5cf81d Merge pull request #6269 from WalterBright/fix16116 fix Issue 16116 - Infinite loop on (somewhat complex) simd math --
[Issue 16710] New: 18003819788 Quickbooks Support phone Number-Quickbooks Tech Suppo
https://issues.dlang.org/show_bug.cgi?id=16710 Issue ID: 16710 Summary: 18003819788 Quickbooks Support phone Number-Quickbooks Tech Suppo Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity: enhancement Priority: P1 Component: dlang.org Assignee: nob...@puremagic.com Reporter: kuldeep.genx2...@gmail.com Intuit:==: 1800 381 9788 Quickbooks Support phone Number@@=1800 381 9788=@@ Quickbooks Tech Support Number=QuickBooks Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number Intuit>1800/381/9788 Quickbooks Support phone Number Quickbooks Tech Support Number QuickBooks Technical Support Number QuickBooks Helpline Number ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ ¶ @ § 18003819788 ௹ Quickbooks Support phone Number Quickbooks Tech Support Number__QuickBooks Technical Support Number ﷼ Desi Dance=@=1.800<381<9788=@= QuickBooks Support Phone NumBER!@!!1-800-381-9788 @@! QuickBooks SuPpoRT 1-800-381-9788 QuickBooks SupPORT PHonE NumbER USA!JEETôßPppu? 1 800 381 9788 QuickBooks SuPpoRT PhoNENumber..,O»G??ô US 1-800-381-9788 QuickBooks help TELEPhoNE Number..,, ??ôQuickBooks help Number..,, ??ôQuickBooks SuPpoRT Number..,, QuickBooks Number..,, QuickBooks PhoNE Number..,, QuickBooks TELEPhoNENumber.. 1-800-381-9788 ,, -qbQuickBooks-technical-support-phone-number-QuickBooks-kumar QuickBooks 24 hourNumber..,, QuickBooks customer SuPpoRT Number..,, QuickBooks tech SuPpoRT PhoNEnumber, Quickbooks Support phone Number Quickbooks Tech Support Number, QuickBooks Help Desk PhoNE Number, QuickBooks SuPpoRT number, QuickBooks SupPORT PHonE NumbER, QuickBooks1-800-381-9788 PhoNEnumber, QuickBooks 1-800-381-9788 SuPpoRT number, QuickBooks SupPORT/QuickBooks-technical-support-number-1-800-381-9788- PHonENumbER. It is very popular toll free number which
[Issue 16709] Error: common.to at common.d conflicts with common.to at common.d
https://issues.dlang.org/show_bug.cgi?id=16709 Timothee Cour changed: What|Removed |Added Keywords|diagnostic | Priority|P3 |P1 Severity|enhancement |regression --- Comment #2 from Timothee Cour --- ok here's a reproducible bug, turns out it's a regression: fun.d: import common3; import common2; void test(){ auto a="12".to!int; } common3.d: module common3; public import common2:to; common2.d: module common2; public: import std.conv; import std.datetime; $dmd_X -c -o- fun.d fun.d(XX): Error: common2.to at common2.d conflicts with common2.to at common2.d $dmd_X --version DMD64 D Compiler v2.072.0 worked with: DMD64 D Compiler v2.067.1 failed with: DMD64 D Compiler v2.068.0 (and DMD64 D Compiler v2.072.0) --
[Issue 16709] Error: common.to at common.d conflicts with common.to at common.d
https://issues.dlang.org/show_bug.cgi?id=16709 Timothee Cour changed: What|Removed |Added CC||timothee.co...@gmail.com --- Comment #1 from Timothee Cour --- update: fun.d(19): Error: common.to at /tmp/common.d conflicts with common.to at /tmp/common.d so it refers to the same file --
[Issue 16709] Error: common.to at common.d conflicts with common.to at common.d
https://issues.dlang.org/show_bug.cgi?id=16709 Vladimir Panteleev changed: What|Removed |Added Hardware|x86 |All OS|Mac OS X|All --
[Issue 16709] Error: common.to at common.d conflicts with common.to at common.d
https://issues.dlang.org/show_bug.cgi?id=16709 Vladimir Panteleev changed: What|Removed |Added Keywords||diagnostic Priority|P1 |P3 CC||thecybersha...@gmail.com --
[Issue 16709] New: Error: common.to at common.d conflicts with common.to at common.d
https://issues.dlang.org/show_bug.cgi?id=16709 Issue ID: 16709 Summary: Error: common.to at common.d conflicts with common.to at common.d Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: enhancement Priority: P1 Component: dmd Assignee: nob...@puremagic.com Reporter: timothee.co...@gmail.com The error message is really hard to understand, and hard to reduce using dustmite (lots of large dependencies). Could we make dmd output more diagnostic information, eg fully qualified name of aliased symbols, eg: ``` module common.d; public import std.conv:to; ``` => Error: common.to(std.conv.to) at common.d conflicts with common.to(...) at common.d --
[Issue 16708] opAssign and struct-member padding break comparison and invariants
https://issues.dlang.org/show_bug.cgi?id=16708 ag0ae...@gmail.com changed: What|Removed |Added CC||ag0ae...@gmail.com --- Comment #2 from ag0ae...@gmail.com --- I'd argue that equality should not compare the padding. See issue 16216. --
[Issue 16680] dmd doesn't use druntime optimized versions of subtraction array operations
https://issues.dlang.org/show_bug.cgi?id=16680 Steven Schveighoffer changed: What|Removed |Added Summary|dmd doesn't use dritime |dmd doesn't use druntime |optimized versions of |optimized versions of |substraction array |subtraction array |operations |operations --
[Issue 16708] opAssign and struct-member padding break comparison and invariants
https://issues.dlang.org/show_bug.cgi?id=16708 Eyal Lotem changed: What|Removed |Added CC||eyal.lo...@gmail.com --- Comment #1 from Eyal Lotem --- Another way to put this is that: x = y; Uses a "fast path" (memcpy) when the type of 'x' doesn't define opAssign, or a "slow path" when the type of 'x' defines opAssign. The fast path does the correct thing and copies fields and padding bytes. The slow path does the wrong thing and calls opAssign to copy fields, but leaves padding bytes potentially uninitialized (which makes some operations *incorrect*, e.g: hashing the object). --
[Issue 16708] opAssign and struct-member padding break comparison and invariants
https://issues.dlang.org/show_bug.cgi?id=16708 ZombineDev changed: What|Removed |Added CC||petar.p.ki...@gmail.com --
[Issue 16708] opAssign and struct-member padding break comparison and invariants
https://issues.dlang.org/show_bug.cgi?id=16708 Tomer Filiba changed: What|Removed |Added Keywords||industry --
[Issue 16708] New: opAssign and struct-member padding break comparison and invariants
https://issues.dlang.org/show_bug.cgi?id=16708 Issue ID: 16708 Summary: opAssign and struct-member padding break comparison and invariants Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: major Priority: P1 Component: dmd Assignee: nob...@puremagic.com Reporter: tomerfil...@gmail.com When a struct defines an opAssign it is obviously "on its own", but it can't possibly assign to the padding (which is something built-in assignment does). Suppose you get the memory for the struct from a memory-pool and you assign a value to it directly. The memory was uninitialized at first, but there are no destructors involved, so there's nothing inherently wrong. Here's an example: import std.stdio; struct MyShort { ushort value; void opAssign(MyShort rhs) nothrow @safe @nogc { value = rhs.value; } } struct YourStruct { MyShort a; int b; } void main() { YourStruct ys1; YourStruct ys2; (cast(ubyte*)&ys2)[0 .. YourStruct.sizeof] = 0xff; writeln("ys1=", (cast(ubyte*)&ys1)[0 .. YourStruct.sizeof]); writeln("ys2=", (cast(ubyte*)&ys2)[0 .. YourStruct.sizeof]); // ys1=[0, 0, 0, 0, 0, 0, 0, 0] // ys2=[255, 255, 255, 255, 255, 255, 255, 255] ys1 = YourStruct(MyShort(17), 18); ys2 = YourStruct(MyShort(17), 18); writeln("ys1=", (cast(ubyte*)&ys1)[0 .. YourStruct.sizeof]); writeln("ys2=", (cast(ubyte*)&ys2)[0 .. YourStruct.sizeof]); // ys1=[17, 0, 0, 0, 18, 0, 0, 0] // ys2=[17, 0, 255, 255, 18, 0, 0, 0]<<< does not assign the padding writeln(ys1.a == ys2.a); // true writeln(ys1.b == ys2.b); // true writeln(ys1 == ys2); // false } So here we get two variables for which memcmp returns != 0, but all their fields are equal. --
[Issue 16680] dmd doesn't use dritime optimized versions of substraction array operations
https://issues.dlang.org/show_bug.cgi?id=16680 ZombineDev changed: What|Removed |Added CC||petar.p.ki...@gmail.com --
[Issue 15064] [CTFE] std.range.enumerate is not CTFE-able
https://issues.dlang.org/show_bug.cgi?id=15064 Paolo Invernizzi changed: What|Removed |Added CC||paolo.inverni...@gmail.com --
[Issue 6125] to!string doesn't throw on invalid UTF sequence
https://issues.dlang.org/show_bug.cgi?id=6125 Lucia Cojocaru changed: What|Removed |Added CC||lucia.mcojoc...@gmail.com --- Comment #3 from Lucia Cojocaru --- Is this a Windows specific bug? I tested the following on Linux 64: 1 import std.conv; 2 import std.stdio; 3 import std.utf; 4 5 void main() 6 { 7 auto x = to!string(cast(char)191); 8 auto z = toUTF8(x); 9 writeln(x); 10 11 12 foreach (y; 0 .. 16) 13 foreach (r; 0 .. 16) 14 { 15 auto buffer = to!string(cast(char)(16 * r + y)); 16 auto b = toUTF8(buffer); 17 writeln(b); 18 //auto result = buffer.toUTF16z; // call to utf16z for the winapi 19 } 20 } Only the commented line throws: core.exception.UnicodeException@src/rt/util/utf.d(292): invalid UTF-8 sequence --
[Issue 16116] Infinite loop on (somewhat complex) simd math
https://issues.dlang.org/show_bug.cgi?id=16116 Walter Bright changed: What|Removed |Added Keywords||pull Severity|normal |major --- Comment #2 from Walter Bright --- https://github.com/dlang/dmd/pull/6269 --
[Issue 16116] Infinite loop on (somewhat complex) simd math
https://issues.dlang.org/show_bug.cgi?id=16116 --- Comment #1 from Walter Bright --- Simpler test case: void foo() { __vector(short[8]) v; int i; v = v * i; } --
[Issue 16707] New: [Templates] run variadic templates example failed
https://issues.dlang.org/show_bug.cgi?id=16707 Issue ID: 16707 Summary: [Templates] run variadic templates example failed Product: D Version: D2 Hardware: All URL: http://dlang.org/ OS: All Status: NEW Severity: normal Priority: P3 Component: dlang.org Assignee: nob...@puremagic.com Reporter: panme...@gmail.com Hi, I am very new to dlang, the following example can't be compiled, my dmd version is "DMD32 D Compiler v2.072.0". https://dlang.org/spec/template.html#variadic-templates template print(args...) { void print() { writeln("args are ", args); // args is a ValueSeq } } template write(Args...) { void write(Args args) // Args is a TypeSeq // args is a ValueSeq { writeln("args are ", args); } } void main() { print!(1,'a',6.8).print();// prints: args are 1a6.8 write!(int, char, double).write(1, 'a', 6.8); // prints: args are 1a6.8 } app.d(31): Error: template app.print cannot deduce function from argument types !()(void), candidates are: app.d(11):app.print(args...)() app.d(32): Error: function app.write!(int, char, double).write (int _param_0, char _param_1, double _param_2) isnot callable using argument types () --
[Issue 16098] align(32) not respected for stack variables
https://issues.dlang.org/show_bug.cgi?id=16098 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #2 from Walter Bright --- (In reply to Ketmar Dark from comment #1) > afair, *any* `align` is simply ignored for stack vars in DMD. No, this is not true, if the align <= the stack alignment. --
[Issue 16092] AVX registers YMM0-YMM7 are inaccessible to 32-bit asm
https://issues.dlang.org/show_bug.cgi?id=16092 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #1 from Walter Bright --- Could you please post sample code that is rejected? --