[Bug c/57647] lvalue required as increment operand

2013-06-19 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57647 --- Comment #7 from vijay Nag --- (In reply to vijay Nag from comment #6) > (In reply to Andreas Schwab from comment #5) > > ((unsigned long*)foo)++ and ((unsigned long *)foo++) are not equivalent > > expressions. The former is the same as foo =

[Bug c/57647] lvalue required as increment operand

2013-06-19 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57647 --- Comment #6 from vijay Nag --- (In reply to Andreas Schwab from comment #5) > ((unsigned long*)foo)++ and ((unsigned long *)foo++) are not equivalent > expressions. The former is the same as foo = (char *)((unsigned long*)foo + > 1), the latte

[Bug c/57647] lvalue required as increment operand

2013-06-19 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57647 --- Comment #4 from vijay Nag --- (In reply to Marek Polacek from comment #3) > It should work for any type, but, why don't you do only foo++;, i.e. drop > the cast? In that case there shouldn't be value computed is not used > warning. Pointer A

[Bug c/57647] lvalue required as increment operand

2013-06-19 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57647 --- Comment #2 from vijay Nag --- (In reply to Marek Polacek from comment #1) > While 4.7 issues warning: value computed is not used, 4.8 and 4.9 do not for > int > main () > { > char bar = 4; > char *foo = &bar; > (unsigned long *)foo++; >

[Bug c/57647] New: lvalue required as increment operand

2013-06-18 Thread vijunag at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: vijunag at gmail dot com I recently upgraded my gcc compiler from 3.4.X to 4.7.2 for my project. Consider the following expression char *foo = &bar; ((unsigned long*)foo)++ While gcc 3.4.X was more forgiving of this issue, 4.7.2 b

[Bug rtl-optimization/57635] gcc hanging while compiling huge files

2013-06-18 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57635 --- Comment #2 from vijay Nag --- With the compiler flag "-fno-var-tracking", it compiles in less than a minute. Although it is quite conspicuous from back-trace I thought it is worth mentioning this info.

[Bug c/57635] gcc hanging while compiling huge files

2013-06-17 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57635 --- Comment #1 from vijay Nag --- Let me know if you will need any additional information. It is also difficult to isolate one single huge file from my project to attach it here. It will be great if you can suggest me to proceed in some direction

[Bug c/57635] New: gcc hanging while compiling huge files

2013-06-17 Thread vijunag at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: vijunag at gmail dot com to gcc Hello, I recently upgraded my compiler to 4.7.2 and I'm trying to compile a huge file containing as much as 92840 lines and gcc is taking an eternity to compile. (more than 18 hours) I see vi

[Bug c++/57531] lvalue required with comma operator

2013-06-05 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57531 --- Comment #5 from vijay Nag --- (In reply to Andrew Pinski from comment #4) > I think the problem is the comma operator causes it to be a rvalue. In that > ((void)0, x) is considered rvalue rather than what you want as a lvalue. > > Note C doe

[Bug c/57531] lvalue required with comma operator

2013-06-05 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57531 vijay Nag changed: What|Removed |Added CC||vijunag at gmail dot com Severity

[Bug c/57531] lvalue required with comma operator

2013-06-05 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57531 --- Comment #3 from vijay Nag --- (In reply to vijay Nag from comment #2) > Sorry for the confusion. Please try the unit test case below > > #include > > /*remove assert in production*/ > > #define ASSERT(x) (void)0 > #define GET_VALUE_A(valu

[Bug c/57531] lvalue required with comma operator

2013-06-05 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57531 vijay Nag changed: What|Removed |Added Component|c++ |c Severity|normal

[Bug c/57531] lvalue required with comma operator

2013-06-04 Thread vijunag at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57531 vijay Nag changed: What|Removed |Added Severity|normal |critical

[Bug c/57531] New: lvalue required with comma operator

2013-06-04 Thread vijunag at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: vijunag at gmail dot com Following expression cannot be compiled using gcc-4.7.2 where as the same statement is perfectly acceptable by gcc version 4.4.5 (void) 0, a = b; [vinag]$ ~/tools/bintools/linux-x86/gcc/201302221200/bin/i686-pc