[Issue 16474] CTFE pow

2018-03-23 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 16474] CTFE pow

2017-12-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 Iain Buclaw changed: What|Removed |Added CC||ibuc...@gdcproject.org

[Issue 16474] CTFE pow

2017-08-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 ki...@gmx.net changed: What|Removed |Added CC||ki...@gmx.net --- Comment #11 from

[Issue 16474] CTFE pow

2017-08-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #10 from uplink.co...@googlemail.com --- (In reply to kinke from comment #9) > > So how does newCTFE interact with CTFloat at the moment? This is an > important piece for cross-compilers. And is there an estimate for when > newCTFE will

[Issue 16474] CTFE pow

2017-08-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #9 from ki...@gmx.net --- (In reply to uplink.coder from comment #7) > (In reply to ZombineDev from comment #6) > > Manu, you may be interested in trying LDC as it will soon support much more > > intrinsics at CTFE than dmd. For

[Issue 16474] CTFE pow

2017-08-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #8 from ZombineDev --- I don't think so, but see the PR for yourself ;) --

[Issue 16474] CTFE pow

2017-08-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #7 from uplink.co...@googlemail.com --- (In reply to ZombineDev from comment #6) > Manu, you may be interested in trying LDC as it will soon support much more > intrinsics at CTFE than dmd. For reference: >

[Issue 16474] CTFE pow

2017-08-05 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 ZombineDev changed: What|Removed |Added CC|

[Issue 16474] CTFE pow

2017-08-02 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #5 from Manu --- True, but that could still be a long way off, and this should have already been working like, 10 years ago... it'd be good to have a default fix in existing ctfe code. --

[Issue 16474] CTFE pow

2017-08-02 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #4 from uplink.co...@googlemail.com --- newCTFE is eventually going to fix that. and other compile-time floating-point issues as well. --

[Issue 16474] CTFE pow

2017-08-02 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #3 from Manu --- Come on... surely it's reasonable to expect all builtin operators should work at ctfe!! ;) --

[Issue 16474] CTFE pow

2016-09-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 --- Comment #2 from Manu --- Sure, or reals, whatever precision the compiler does floating point constant folding would be fine. --

[Issue 16474] CTFE pow

2016-09-09 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16474 uplink.co...@googlemail.com changed: What|Removed |Added CC||uplink.co...@googlemail.com