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: Allocate a variable in a known physical location

From: Fabian Cenedese <Cenedese at indel dot ch>
To: gcc-help at gcc dot gnu dot org
Date: Fri, 04 Feb 2011 13:16:51 +0100
Subject: Re: Allocate a variable in a known physical location
References: <AANLkTinC_Z4N3Yc26Naf88_ZCFVo6v6pSv2WrzGo+DXw@mail.gmail.com>

At 03:59 04.02.2011 -0800, isuru herath wrote:
>Hi Brian,
>
>Again sorry for the late response. I was doing more testing. I followed 
>your suggestion. But, I think you need to change this to following since 
>they are pointers. Fabi's suggestion was the same. However results don't 
>change.

Have you ever checked what assembler code is generated? There you
should see the accesses, why they're made and possibly how to avoid them.

bye  Fabi

References:
- Re: Allocate a variable in a known physical location
  - From: Brian Budge
- Re: Allocate a variable in a known physical location
  - From: isuru herath

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