* 32-bit memory models
@ 2006-06-22 22:54 Young, Michael
2006-06-23 3:25 ` Ian Lance Taylor
0 siblings, 1 reply; 2+ messages in thread
From: Young, Michael @ 2006-06-22 22:54 UTC (permalink / raw)
To: gcc-help
I'm looking for a definitive answer, and I can't seem to find anything in the docs on this... Does GCC/G++ support segment:offset (48-bit) pointers for protected mode 32-bit programming on 32-bit Intel processors? I'd like to use a "compact" memory model, where code is "near" (in the same segment), but data pointers are "far" (by default, with an option to explicitly override using a "near/far" keyword modifier. This is similar to traditional 16-bit memory models (Intel ABI), except that the offsets are full 32-bits and segments don't necessarily refer to overlapping memory space. The reason I'm looking to do this is that I want to develop an OS feature using security provided via the LDT, and I'd like to avoid having to revert to assembler every time I need to look at memory using a different selector. (If this topic is in the documentation, please point me to the right place!)
Thanks,
Mike
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 32-bit memory models
2006-06-22 22:54 32-bit memory models Young, Michael
@ 2006-06-23 3:25 ` Ian Lance Taylor
0 siblings, 0 replies; 2+ messages in thread
From: Ian Lance Taylor @ 2006-06-23 3:25 UTC (permalink / raw)
To: Young, Michael; +Cc: gcc-help
"Young, Michael" <Michael.Young@paetec.com> writes:
> I'm looking for a definitive answer, and I can't seem to find
> anything in the docs on this... Does GCC/G++ support segment:offset
> (48-bit) pointers for protected mode 32-bit programming on 32-bit
> Intel processors?
No. Sorry.
Ian
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-06-23 3:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-06-22 22:54 32-bit memory models Young, Michael
2006-06-23 3:25 ` Ian Lance Taylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).