* Internal compiler error in 2.4.5 (hacky workaround)
@ 2002-02-11 20:15 Pavel Machek
2002-02-12 9:47 ` Arjan van de Ven
0 siblings, 1 reply; 2+ messages in thread
From: Pavel Machek @ 2002-02-11 20:15 UTC (permalink / raw)
To: kernel list
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
--
(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
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Internal compiler error in 2.4.5 (hacky workaround)
2002-02-11 20:15 Internal compiler error in 2.4.5 (hacky workaround) Pavel Machek
@ 2002-02-12 9:47 ` Arjan van de Ven
0 siblings, 0 replies; 2+ messages in thread
From: Arjan van de Ven @ 2002-02-12 9:47 UTC (permalink / raw)
To: Pavel Machek; +Cc: linux-kernel
Pavel Machek wrote:
>
> 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;
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).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-02-12 9:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-11 20:15 Internal compiler error in 2.4.5 (hacky workaround) Pavel Machek
2002-02-12 9:47 ` Arjan van de Ven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®