Skip to contentSkip to conversation

Internal compiler error in 2.4.5 (hacky workaround)

DISCUSSION Pavel Machek 2 participants 2 messages Feb 12, 2002

lore
Share & tools
lore
#0 lore raw

Hi!

This makes gcc survive... adding volatile everywhere ;-).

int blk_ioctl(volatile kdev_t dev, volatile unsigned int cmd, volatile unsigned long arg)

{
        volatile request_queue_t *q;
        volatile struct gendisk *g;
        volatile u64 ullval = 0;
        volatile int intval, *iptr;
        volatile unsigned short usval;

									Pavel
Signature · 2 lines
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
#1 lore raw
Quoted 5 lines · Pavel Machek

Hi!

This makes gcc survive... adding volatile everywhere ;-).

Quoted 8 lines

int blk_ioctl(volatile kdev_t dev, volatile unsigned int cmd, volatile unsigned long arg)

{
        volatile request_queue_t *q;
        volatile struct gendisk *g;
        volatile u64 ullval = 0;
        volatile int intval, *iptr;
        volatile unsigned short usval;

For 2.4 I can see such a workaround being accepted; however for 2.5 I would say
to keep the code clean of such things and rather get the compiler fixed (or the
specific version depricated).