RE: Is this a bug in gcc??

RE: Is this a bug in gcc??

[Martin York]

 Name lastlong wrote:
> Hi,
> 
> I am expecting a error (redefinition of "a") from following piece of 
> code. But gcc (3.4.2) doesnot give any error.
> /////////////////
> int a;
> char b;
> int a;

Just to expand on what has already been said.
gcc/g++ behave as required by the standard. But to make sure we compare
apples to apples.

If you add the above to the file: test.c

gcc -c test.c   # Works Fine     (as expected)
g++ -c test.c   # Outputs errors (as expected)

Note that gcc is a C compiler (or should I say invokes the underlying C
Compiler by default) while g++ is a C++ compiler. NB If you name the
file test.cpp the content is C++ and the C++ compiler will be invoked no
matter how 'Gcc' is invoked (unless you explicitly override the
defaults).

Re: Assembly optimizations

[Nathan Sidwell]

Klaus Winter wrote:
> Hi all,
> 
> I compiled the following code with gcc-3.3.1. Once without
> optimization and one time with optimization -O. With optimization the
> Decrement function takes a LOT longer than before whereas the
> Increment function stays constant. I haven't found anything in the
> manpage about it ... Any help is appreciated.
> 
> cheers,
> Klaus
> 
> #include <stdio.h>
> #include <time.h>
> #include <sys/time.h>
> 
> int g_Lock_Mini = 0;
> 
> inline int Increment( int* count)
> {
> 	__asm__ __volatile__( "movl $1, %%eax\n\t" 
> 			      "lock; xaddl %%eax, (%%ecx)\n\t"
> 			      "incl %%eax\n\t" : : "c" (count) );
> }
> inline int Decrement( int * count)
> {
> 	__asm__ __volatile__( "lock; decl (%%ecx)\n\t"
> 				  "movl (%%ecx), %%eax\n\t" : : "c" (count));
> }
these asms are broken. I think you want something like

asm volatile("lock;decl (%1)\n\tmovl (%1),%0" : "=r" (result) : "r" (count) : "memory")

gcc does not otherwise know what registers are used by the asm.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

Is this a bug in gcc??

[Name lastlong]

Hi,

I am expecting a error (redefinition of "a") from
following piece of code. But gcc (3.4.2) doesnot give
any error.
/////////////////
int a;
char b;
int a;

void foo(void)
{
return;
}
/////////////////
Instead, if we try initialising "a" at BOTH the
places, then it gives error.
VC++ gives this error anyway.

Is it a bug???

Regards.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Is this a bug in gcc??

[Nathan Sidwell]

Name lastlong wrote:
> Hi,
> 
> I am expecting a error (redefinition of "a") from
> following piece of code. But gcc (3.4.2) doesnot give
> any error.
> /////////////////
> int a;
> char b;
> int a;
> 
> void foo(void)
> {
> return;
> }
> /////////////////
> Instead, if we try initialising "a" at BOTH the
> places, then it gives error.
> VC++ gives this error anyway.

VC++ is a C++ compiler, where the above is an error
gcc is a C compiler, where the above is not an error

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

Re: Is this a bug in gcc??

[Name lastlong]

Ok agreed!

But don't you think that C compiler (gcc) also output
this error? 
My observation is gcc outputs error only if we try to
initialise both instant of "a".

Regards.

--- Nathan Sidwell <nathan@codesourcery.com> wrote:

> Name lastlong wrote:
> > Hi,
> > 
> > I am expecting a error (redefinition of "a") from
> > following piece of code. But gcc (3.4.2) doesnot
> give
> > any error.
> > /////////////////
> > int a;
> > char b;
> > int a;
> > 
> > void foo(void)
> > {
> > return;
> > }
> > /////////////////
> > Instead, if we try initialising "a" at BOTH the
> > places, then it gives error.
> > VC++ gives this error anyway.
> 
> VC++ is a C++ compiler, where the above is an error
> gcc is a C compiler, where the above is not an error
> 
> nathan
> 
> -- 
> Nathan Sidwell    ::   http://www.codesourcery.com  
> ::     CodeSourcery LLC
> nathan@codesourcery.com    ::    
> http://www.planetfall.pwp.blueyonder.co.uk
> 
> 



	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

Re: Is this a bug in gcc??

[Eljay Love-Jensen]

Hi Name lastlong,

 >But don't you think that C compiler (gcc) also output this error?

It's not an error in C, therefore a C compiler would be non-compliant to 
the C standard if it produced an error.  (And it would break a lot of 
correct code.)

 >My observation is gcc outputs error only if we try to initialise both 
instant of "a".

In C, there is only one instance of "a".

Stroustrup talks about C/C++ incompatibility in his C++ Programming 
Language (3rd and Special editions) on B.2.2.

HTH,
--Eljay

Re: Is this a bug in gcc??

[Name lastlong]

Hi Eljay Love-Jensen,

Thanks a lot for ur reply. 
I understand it this time. :)

Regards,
Brew.

--- Eljay Love-Jensen <eljay@adobe.com> wrote:

> Hi Name lastlong,
> 
>  >But don't you think that C compiler (gcc) also
> output this error?
> 
> It's not an error in C, therefore a C compiler would
> be non-compliant to 
> the C standard if it produced an error.  (And it
> would break a lot of 
> correct code.)
> 
>  >My observation is gcc outputs error only if we try
> to initialise both 
> instant of "a".
> 
> In C, there is only one instance of "a".
> 
> Stroustrup talks about C/C++ incompatibility in his
> C++ Programming 
> Language (3rd and Special editions) on B.2.2.
> 
> HTH,
> --Eljay
> 
> 



		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com 

Re: Is this a bug in gcc??

[Nathan Sidwell]

Name lastlong wrote:
> Ok agreed!
> 
> But don't you think that C compiler (gcc) also output
> this error? 
if it did that, it would not be a C compiler.  What part
of 'gcc is a C compiler, where the above is not an error'
was unclear?

> My observation is gcc outputs error only if we try to
> initialise both instant of "a".
again, correct. doing that is an error in C

nathan
-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk