[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-03 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 --- Comment #1 from Jonathan Wakely --- I believe GCC is right, as unhelpful as that might seem.

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread mick.pearson at wildblue dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 --- Comment #2 from Mick P. --- Of course, GCC is always right. Even though other types are not considered candidates for indexing the array, when the only other use of [] is operator[], which accepys any type... and switch statements should try

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 --- Comment #4 from Jonathan Wakely --- All compilers agree, because it's what the standard says should happen.

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread mick.pearson at wildblue dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Mick P. changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #5 from Mick P. --- Try Vis

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread mick.pearson at wildblue dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Mick P. changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #6 from Mick P. --- Should

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-04 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Andrew Pinski changed: What|Removed |Added Resolution|FIXED |INVALID --- Comment #7 from Andrew Pinsk

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-05 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 --- Comment #8 from Jonathan Wakely --- (In reply to Mick P. from comment #5) > Try Visual Studio's. I did, and it doesn't compile: https://godbolt.org/z/Q54kFs

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-05 Thread mick.pearson at wildblue dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Mick P. changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #9 from Mick P. --- I began

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-05 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |INVALID

[Bug c++/92338] double/float thought (ambiguous) candidate for C-array index. (Non numeric types aren't.)

2019-11-05 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92338 --- Comment #10 from Jonathan Wakely --- Can you please stop changing the status to FIXED. That means a bug in GCC was fixed. Since nothing in GCC changed, nothing has been fixed. I think all compilers are trying to convert the object to std::pt