Try compiling the said code with -fno-strict-aliasing, and your problems
will be solved.  gcc is doing the right thing, just not what you expected.

The kernel already checks to see if gcc can grok -fno-strict-aliasing

Aaron

On 23 Oct 2000, David Wragg wrote:

> Gregory Maxwell <[EMAIL PROTECTED]> writes:
> > If 2.96 is broken, I'd appreciate it if you would describe the breakage. 
> 
> As in the RedHat 2.96?  Try compiling the following on RedHat 7.0 x86
> with "gcc -O2" and take a look at the generated code.  Nice, isn't it?
> 
> 
> #include <sys/time.h>
> 
> void foo(void)
> {
>                 struct itimerval iv;
>                 
>                 iv.it_interval.tv_sec = 0;
>                 iv.it_interval.tv_usec = 250000;
>                 iv.it_value = iv.it_interval;
> 
>                 setitimer(ITIMER_REAL, &iv, NULL);
> }

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Reply via email to