This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Null pointer dereference and side effects

From: Alexandre Oliva <aoliva at redhat dot com>
To: Eljay Love-Jensen <eljay at adobe dot com>
Cc: Archie Cobbs <archie at dellroad dot org>, gcc-help at gcc dot gnu dot org
Date: 22 Jul 2004 17:24:40 -0300
Subject: Re: Null pointer dereference and side effects
Organization: Red Hat Global Engineering Services Compiler Team
References: <200407201512.i6KFCXrx001516@arch20m.dellroad.org><or1xj5507j.fsf@livre.redhat.lsd.ic.unicamp.br><6.1.1.1.2.20040721063035.021e7958@iplan-mn.corp.adobe.com>

On Jul 21, 2004, Eljay Love-Jensen <eljay@adobe.com> wrote:

> Making what the pointer points to volatile:

> volatile int * p;

Sorry, this is what I meant.  Although making the pointer volatile
would actually force the memory location holding the pointer to be
loaded, it wouldn't force the memory location it points to to remain.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

References:
- Re: Null pointer dereference and side effects
  - From: Archie Cobbs
- Re: Null pointer dereference and side effects
  - From: Alexandre Oliva
- Re: Null pointer dereference and side effects
  - From: Eljay Love-Jensen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]