https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97658
--- Comment #3 from hubert.vansteenhuyse at freecode dot be ---
You are killing that marvelous gcc compiler by doing this, this is my point.
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: hubert.vansteenhuyse at freecode dot be
Target Milestone: ---
src/MAL/utils/utils.hpp:600:10: note: ‘struct
HASHTABLE::CONTAINER’ declared here
600 | struct CONTAINER
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60213
hubert.vansteenhuyse at freecode dot be changed:
What|Removed |Added
Status|WAITING |RESOLVED
++
Assignee: unassigned at gcc dot gnu.org
Reporter: hubert.vansteenhuyse at freecode dot be
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60213
--- Comment #1 from hubert.vansteenhuyse at freecode dot be ---
struct A {
A *a[2];
A() { a[0] = 0; a[1] = 0; }
~A(){ if(a[0]) delete a[0]; if(a[1]) delete a[1];
}
void main(){
A *a = new A();
a-a[0] = new A();
a-a[1] = new A();
delete
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60213
--- Comment #3 from hubert.vansteenhuyse at freecode dot be ---
(In reply to Marc Glisse from comment #2)
Your example is bogus: { and } don't match, main must return int, etc. If I
fix it so it compiles, I don't see any crash.
Of course
