optimization/6673: gcc-3.1 produces wrong assembly code

[Nam SungHyun]

rth@gcc.gnu.org wrote:
> Synopsis: gcc-3.1 produces wrong assembly code
> 
> State-Changed-From-To: feedback->closed
> State-Changed-By: rth
> State-Changed-When: Thu May 16 19:12:57 2002
> State-Changed-Why:
>     As diagnosed, not a bug.

I saw the feed back message from the gnats web, but did not get a
mail. Did not know how I can reply for that feedback.

I just wanted to be sure:

    the 'a' in my example source is a 'global variable'.
    So, should the gcc treat it as a volatile by default?
    There are so many multi-threaded program. I didn't see
    any program which use volatile for the global variable.

Regards,

namsh