From: Mike Frysinger Date: Tue, 17 Mar 2009 14:38:03 -0400 Subject: [U-Boot] [PATCH] 8313erdb: Set guarded bit on BAT that covers the end of the address space. In-Reply-To: References: <20090317170931.GA14779@ld0162-tx32.am.freescale.net> <200903171407.29266.vapier@gentoo.org> Message-ID: <200903171438.05654.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday 17 March 2009 14:13:39 Kumar Gala wrote: > >>> if C code is doing ptr checks, the compiler should make sure that > >>> pointer is not dereferenced at all if the hardware cannot suffer the > >>> consequences, even speculatively. > >> > >> There is no reasonable way for the compiler to prevent such > >> speculative > >> accesses. Non-memory-like mappings must have the guarded bit set. > >> That > >> is what the bit is there for. > > > > if the hardware doesnt have a way of preventing it, then the > > compiler must nop > > bad accesses that are unknown. > > > > i'm not sure your example proves your position. if you have a > > region that > > cannot stand speculative access, how do you handle bad pointer > > checking if the > > compiler may generate code that'll speculatively hit it at any time ? > > This has nothing to do w/the compiler but how HW speculation actually > works. > > If you don't understand that say so and ask about it.. Dont try and > claim Scott's example and patch aren't valid because they are. i never said Scott's proposed change was wrong -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20090317/77bc36d0/attachment-0001.pgp