Assignee: unassigned at gcc dot gnu.org
Reporter: srinivas.sundar at vvdntech dot in
Target Milestone: ---
Here is my sample kernel code. which works fine in gcc-4, had an issue with
gcc-5. I get both the print even if I allocate the dynamic memory to
kern_buff_p.
Disassemble of code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86092
--- Comment #2 from Srinivas Achary ---
Sorry that I am new to this.
Is there any possibility to make this code work, without changing the variable
attribute. GCC-4 has no issue with this code. What special flags have been
included in the GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86092
Srinivas Achary changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86092
--- Comment #5 from Srinivas Achary ---
thank you Marc.
What I have shown here is just an example sample code. But I have code which
makes use of kern_buff_p variable in many place.If I use volatile that might
reduce my code speed.
Any how the k
: unassigned at gcc dot gnu.org
Reporter: srinivas.sundar at vvdntech dot in
Target Milestone: ---
int main()
{
unsigned long ul=4294967296;
unsigned int var;
var=ul; // how to get warning
}
The value of "var" will be different in 64bit system and 32bit system. Is it
p
