|
Message
From: György 'nog' Jeney<nog@s...>
Date: Wed Jan 26 19:29:27 CET 2005
Subject: [openrisc] [or1ksim #7] Stricter typeing...
Hi,I'm not sure how this patch shall be received but I believe this is the way to go. I have introduced 2 new types:
oraddr_t and orreg_t
oraddr_t is used to mark addresses that the simulated processor (and peripherals) address. This is basically a reqirement to implement a 64-bit simulator (no, I'm not going to do that anytime soon). I have also defined the formating macros for these new types (PRIxADDR and PRIxREG), (What C99 has done in inttypes.h). I realise that this header and macros may not be availible on some varients of unix, but I don't know, so if you know of a place were the simulator might be used and these types are not availible, then shout and I'll stick in a configure check to fix it.
While doing all these changes I noticed that eval_direct{8,16,32} has this comment:
`/* for simulator accesses, the ones that cpu wouldn't do'
but in the those functions we raise an exception if the memory area is not valid. Is this really a good idea? If the cpu wouldn't do the access then there wouldn't be an exception...
ChangeLog: * Mark a simulated cpu address as such, by introducing the new oraddr_t type.
nog. -------------- next part -------------- A non-text attachment was scrubbed... Name: patch7.gz Type: application/x-gunzip Size: 25434 bytes Desc: not available Url : patch7-0001.bin
|
 |