[Issue 13652] 2D Static Array Init produces wrong result (-m64/-m32)
https://issues.dlang.org/show_bug.cgi?id=13652 Kenji Hara changed: What|Removed |Added Keywords||pull, wrong-code Hardware|x86_64 |All --- Comment #2 from Kenji Hara --- https://github.com/D-Programming-Language/dmd/pull/5034 --
[Issue 15011] New: can override public method with protected method
https://issues.dlang.org/show_bug.cgi?id=15011
Issue ID: 15011
Summary: can override public method with protected method
Product: D
Version: D2
Hardware: x86_64
OS: Windows
Status: NEW
Severity: minor
Priority: P1
Component: dmd
Assignee: nob...@puremagic.com
Reporter: yosik...@altalk.com
following code prints 'Foo2'
expected result is compile error.
DMD32 D Compiler v2.068.0
file main.d:
import foo;
void main() {
Foo1 foo = new Foo2();
foo.bar();
}
file foo.d:
import std.stdio;
class Foo1 {
void bar() {
writeln("Foo1");
}
};
class Foo2 : Foo1 {
protected override void bar() {
writeln("Foo2");
}
};
--
[Issue 15011] can override public method with protected method
https://issues.dlang.org/show_bug.cgi?id=15011 yosik...@altalk.com changed: What|Removed |Added CC||yosik...@altalk.com --
[Issue 13017] opEquals for null std.typecons.Nullable
https://issues.dlang.org/show_bug.cgi?id=13017
Tomáš Chaloupka changed:
What|Removed |Added
CC||chalu...@gmail.com
--- Comment #1 from Tomáš Chaloupka ---
Similar problem, same exception:
import std.typecons;
struct Foo
{
Nullable!int field;
}
void main()
{
Foo a;
assert (a == Foo.init);
}
--
[Issue 13652] 2D Static Array Init produces wrong result (-m64/-m32)
https://issues.dlang.org/show_bug.cgi?id=13652 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/83372faf1b925d94fe68bd3b9c31abb346bb2e6b fix Issue 13652 - 2D Static Array Init produces wrong result (-m64/-m32) https://github.com/D-Programming-Language/dmd/commit/30c67419c0b646c13b5a511b80c22b1d579e1793 Merge pull request #5034 from 9rnsr/fix13652 Issue 13652 - 2D Static Array Init produces wrong result (-m64/-m32) --
[Issue 13652] 2D Static Array Init produces wrong result (-m64/-m32)
https://issues.dlang.org/show_bug.cgi?id=13652 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 15012] New: Druntime Makefile whitelists compilers
https://issues.dlang.org/show_bug.cgi?id=15012 Issue ID: 15012 Summary: Druntime Makefile whitelists compilers Product: D Version: D2 Hardware: All OS: Linux Status: NEW Severity: regression Priority: P1 Component: druntime Assignee: c...@dawg.eu Reporter: thecybersha...@gmail.com https://github.com/D-Programming-Language/druntime/pull/1317 added a whitelist of compiler binaries for which to add certain CFLAGS. This precludes e.g. using wrapper scripts to work around issue 12572. This issue is blocking some of my work on D (I can't bisect certain bugs or build D on certain machines). Introduced in https://github.com/D-Programming-Language/druntime/pull/1317 I've notified the PR author in a comment on the PR five days ago, but no reply: https://github.com/D-Programming-Language/druntime/pull/1317#discussion_r38268116 --
[Issue 15006] Compiling trivial program produces 400,000+ byte object file
https://issues.dlang.org/show_bug.cgi?id=15006 Vladimir Panteleev changed: What|Removed |Added CC||thecybersha...@gmail.com --- Comment #2 from Vladimir Panteleev --- Can't reproduce with 2.068 with either -m32 or -m64 --
[Issue 15005] Coverage files start with a dash character when using full pathname for source files with -cov
https://issues.dlang.org/show_bug.cgi?id=15005 Vladimir Panteleev changed: What|Removed |Added CC||thecybersha...@gmail.com --- Comment #1 from Vladimir Panteleev --- Workaround: use ./-path-to-my-file.lst --
[Issue 14959] Regression in HEAD: linker error on printing SysTime with writeln
https://issues.dlang.org/show_bug.cgi?id=14959 --- Comment #9 from Jack Stouffer --- (In reply to Vladimir Panteleev from comment #8) > Can you try building D with Digger? > > https://github.com/CyberShadow/Digger Unfortunately, every time I try to use digger, the build fails even though github loads just fine in my browser: Cloning into 'dmd'... fatal: unable to connect to github.com: github.com[0: 192.30.252.130]: errno=Operation timed out Clone of 'git://github.com/D-Programming-Language/dmd' into submodule path 'dmd' failed digger: Not caching build failure due to temporary/environment error. Fatal error: Command ["git", "--work-tree=/Users/Jack/dlang_contrib/test_dir/repo", "--git-dir=/Users/Jack/dlang_contrib/test_dir/repo/.git", "submodule", "update", "--init", "dmd"] failed with status 1 --
[Issue 14959] Regression in HEAD: linker error on printing SysTime with writeln
https://issues.dlang.org/show_bug.cgi?id=14959 --- Comment #10 from Vladimir Panteleev --- (In reply to Jack Stouffer from comment #9) > Unfortunately, every time I try to use digger, the build fails even though > github loads just fine in my browser: > > Cloning into 'dmd'... > fatal: unable to connect to github.com: > github.com[0: 192.30.252.130]: errno=Operation timed out Unblock TCP port 9418 or run: git config --global url.https://github.com/.insteadOf git://github.com/ --
[Issue 14959] Regression in HEAD: linker error on printing SysTime with writeln
https://issues.dlang.org/show_bug.cgi?id=14959 --- Comment #12 from Vladimir Panteleev --- (In reply to Jack Stouffer from comment #11) > Works with digger build. I'm not quite sure what that means. Am I manually > building DMD wrong? It means that the way in which Digger builds D and the way you build D result in different outcomes. You could look through Digger's log, see how it builds D and try to find the difference with your method. It could also be an installation problem (mismatching versions of the compiler and Phobos, or Phobos library and Phobos source code, or an outdated version of one of the above being in front of the just-built version in the search path). --
[Issue 14959] Regression in HEAD: linker error on printing SysTime with writeln
https://issues.dlang.org/show_bug.cgi?id=14959 --- Comment #11 from Jack Stouffer --- (In reply to Vladimir Panteleev from comment #10) > (In reply to Jack Stouffer from comment #9) > > Unfortunately, every time I try to use digger, the build fails even though > > github loads just fine in my browser: > > > > Cloning into 'dmd'... > > fatal: unable to connect to github.com: > > github.com[0: 192.30.252.130]: errno=Operation timed out > > Unblock TCP port 9418 or run: > > git config --global url.https://github.com/.insteadOf git://github.com/ Works with digger build. I'm not quite sure what that means. Am I manually building DMD wrong? --
[Issue 14959] Regression in HEAD: linker error on printing SysTime with writeln
https://issues.dlang.org/show_bug.cgi?id=14959 Jack Stouffer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #13 from Jack Stouffer --- (In reply to Vladimir Panteleev from comment #12) > (In reply to Jack Stouffer from comment #11) > > Works with digger build. I'm not quite sure what that means. Am I manually > > building DMD wrong? > > It means that the way in which Digger builds D and the way you build D > result in different outcomes. You could look through Digger's log, see how > it builds D and try to find the difference with your method. > > It could also be an installation problem (mismatching versions of the > compiler and Phobos, or Phobos library and Phobos source code, or an > outdated version of one of the above being in front of the just-built > version in the search path). Because I am going to assume digger is more correct that my build I will close this. Where can I find said log file? --
[Issue 14959] Regression in HEAD: linker error on printing SysTime with writeln
https://issues.dlang.org/show_bug.cgi?id=14959 --- Comment #14 from Vladimir Panteleev --- Terminal output. You can redirect it to a file e.g. with "2>&1 | tee digger.log". --
[Issue 14975] DMD refuses to inline even trivial struct constructors
https://issues.dlang.org/show_bug.cgi?id=14975 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 14975] DMD refuses to inline even trivial struct constructors
https://issues.dlang.org/show_bug.cgi?id=14975 --- Comment #5 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/545572134f613433f0efe3aaa247b3f401a02aa9 fix Issue 14975 - DMD refuses to inline even trivial struct constructors https://github.com/D-Programming-Language/dmd/commit/68650c1df4608a10be47e5cfe0610babe7bd2f47 Merge pull request #5033 from WalterBright/fix14975 fix Issue 14975 - DMD refuses to inline even trivial struct constructors --
[Issue 14673] BigInt needs more performance and total revision
https://issues.dlang.org/show_bug.cgi?id=14673 Jack Stouffer changed: What|Removed |Added Keywords||performance CC||j...@jackstouffer.com --
[Issue 14562] Support BigInt function std.range.repeat and other functions of Phobos
https://issues.dlang.org/show_bug.cgi?id=14562 Jack Stouffer changed: What|Removed |Added CC||j...@jackstouffer.com --- Comment #1 from Jack Stouffer --- (In reply to dennis.m.ritchie from comment #0) > I believe that the repeat function and other functions of Phobos, where the > use BigInt appropriate, should support BigInt. Doing c.repeat(b) works. Honest question: do you really need the second param to also be a BigInt? --
[Issue 11252] "in" operator for std.range.iota
https://issues.dlang.org/show_bug.cgi?id=11252 Jonathan M Davis changed: What|Removed |Added CC||issues.dl...@jmdavisprog.co ||m --- Comment #3 from Jonathan M Davis --- in must be no worse than O(log n) or it is inappropriate to use it. And given how iota works, that can't possibly be done in anything better than O(n) in the general case, though it would be possible to implement it for integers specifically. Honestly though, this seems like an abuse of the in operator to me. in is really intended for lookup in containers. It's definitely not a range operation. A better alternative would be to add find/canFind as a member function to iota in the cases where it would be more efficient than the std.algorithm implementation. Then any code which uses find/canFind with UFCS with iota and integral values would get a performance boost (including in generic code) rather than just this specific case where the code is specifically written for iota. --
[Issue 12744] auto ref crashes DMD on ASSERT
https://issues.dlang.org/show_bug.cgi?id=12744 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/8f03ee45f9df1a0fdcca492cac575ab0d0b3fff0 fix Issue 12744 - auto ref crashes DMD on ASSERT https://github.com/D-Programming-Language/dmd/commit/37ee74a59eec69e48595c79f0f1340c9e1d637cf Merge pull request #5032 from 9rnsr/fix12744 Issue 12744 - auto ref crashes DMD on ASSERT --
[Issue 12744] auto ref crashes DMD on ASSERT
https://issues.dlang.org/show_bug.cgi?id=12744 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 15013] New: std.mmfile module produces bus error at certain conditions
https://issues.dlang.org/show_bug.cgi?id=15013
Issue ID: 15013
Summary: std.mmfile module produces bus error at certain
conditions
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: phobos
Assignee: nob...@puremagic.com
Reporter: sdegtia...@yahoo.com
std.MmFile when opens file in read only mode never expands it, even if memory
requested is bigger than actual file size.
When the allocated memory is less than one system page, it passes because
mmap() allocates shared memory by page. If however, requested size is bigger
than one page, any attempt to read from addresses above page size results to
BusError.
Code to illustrate:
unittest // issue: read-only file is not extended
{
auto fn=deleteme;
scope(exit) std.file.remove(fn);
/// create new very short file
{ File(fn,"w").write("123"); }
/** Trying to map more than one page
* The file is not resized and only one page is allocated
* Now, the last half of the slice has not valid mapping
**/
auto n=new MmFile(fn, MmFile.Mode.read, 0x1020, null);
auto k=cast(int[]) n[];
/// Bus error here
auto y=k[$-1];
}
--
