<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/10/2014 11:15 AM, Talin wrote:<br>
</div>
<blockquote
cite="mid:CABwJDdkc8txMt0+LjO-LjVvcBS5Onq2J9qtx2Zc+_5mzF-=rmA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
We currently use address spaces on our architecture to
differentiate between traditional pointers and fat
pointers (both of which are supported on our system in
hardware). It would be nice, rather than hard-coding
an address space, to have a property on DataLayout
that would tell you if a specific address space
contained GC pointers. We could then designate an
address space that was both GCable and contained fat
pointers, and another for non-GCable fat pointers.<br>
</blockquote>
</div>
Making this configurable is definitely desirable. I like
your idea of including a list of address spaces in data
layout which contain GC pointers and making that
query-able. That sounds quite reasonable. Unless anyone
makes another proposal, I'll run with this.</blockquote>
<div><br>
</div>
<div>Does it need to be a list, or could it be a range? It
the set of GC address spaces was contiguous over some
range of integers, then you'd only need to store a min /
max value, which might make the implementation simpler. <br>
</div>
</div>
</div>
</div>
</blockquote>
A range is also fine. David, does that meet your use case as well?<br>
<br>
Philip<br>
</body>
</html>