https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63642
--- Comment #4 from Romain ---
Created attachment 33808
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33808&action=edit
The right version
I am sorry, but the file I've attached in my last message was not the right
version.
Here is the rig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63642
--- Comment #2 from Romain ---
Created attachment 33807
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33807&action=edit
A test for the bug about linked list
Here is an example of the problem I have encoutered.
It is unfortunately written
erity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: romain.wallon at orange dot fr
Created attachment 33806
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33806&action=edit
A program which tests changing a const
: c
Assignee: unassigned at gcc dot gnu.org
Reporter: romain.wallon at orange dot fr
In a linked list, the pointer to the next element seems to always point to
itself : when the list->next is assigned to null, list is also assigned to
null.
It happens on the gcc version on