[Bug other/81334] New: -Wmisleading-indentation

2017-07-05 Thread mick.pearson at wildblue dot net
Assignee: unassigned at gcc dot gnu.org Reporter: mick.pearson at wildblue dot net Target Milestone: --- "note: -Wmisleading-indentation is disabled from this point onwards, since column-tracking was disabled due to the size of the code/headers if(Min<0) Min = 0; if(Max

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

2019-11-03 Thread mick.pearson at wildblue dot net
IRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mick.pearson at wildblue dot net Target Milestone: --- A double (float) conversion is considered candidate for indexing a C-array. A double (float)

[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 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 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-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++/97710] New: Help with breaking change? cast point-to-member address in template parameter list

2020-11-03 Thread mick.pearson at wildblue dot net via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mick.pearson at wildblue dot net Target Milestone: --- GCC used to agree with MSVC in letting pointer-to-member addresses be cast inside templates, i.e. compile time

[Bug c++/97710] Help with breaking change? cast pointer-to-member address in template parameter list

2020-11-04 Thread mick.pearson at wildblue dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97710 --- Comment #2 from Mick P. --- Sorry, I may have jumped to conclusion. I think there's a different problem that goes like: struct A{}; struct B:A{ int x; }; struct C:A{ T y; }; So T expects a pointer-to-member from A but will not cast (in temp

[Bug c++/97710] Help with breaking change? cast pointer-to-member address in template parameter list

2020-11-04 Thread mick.pearson at wildblue dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97710 --- Comment #4 from Mick P. --- Sorry, here is an example diagnostic. The reason I couldn't follow it yesterday is "make -j4" was causing the output to be scrambled. >/home/Michael/collada/dom/include/dae/domAny.h:62:33: error: >'reinterpret_ca

[Bug c++/97710] Help with breaking change? cast pointer-to-member address in template parameter list

2020-11-04 Thread mick.pearson at wildblue dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97710 --- Comment #5 from Mick P. --- EDITED: In my example/link I changed the type from "int" to "char" by mistake, but actually it shouldn't matter and using "int" produces even stranger results that maybe should be investigated (using char for both

[Bug c++/97710] Help with breaking change? cast pointer-to-member address in template parameter list

2020-11-04 Thread mick.pearson at wildblue dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97710 --- Comment #6 from Mick P. --- Desired scenario: https://godbolt.org/z/zKnh1s template struct T{}; struct A{}; struct B:A{ int x; }; struct C:A{ T y; }; Changing x to char yields the other diagnostic. PtoM types are fungible, I don't know why