<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/26/2015 07:02 PM, Chandler
Carruth via llvm-dev wrote:<br>
</div>
<blockquote
cite="mid:CAGCO0KipUBD3WYPJFmE5HOyE6KuGcJU0RMD=cbJyEfk_w-_yjg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div class="gmail_quote"><br>
<div>Without a better understanding of both the motivation and
the resulting consequences such as what I've outlined in my
questions above, it is very hard for me to feel comfortable
with this kind of change.</div>
<br>
</div>
</div>
</blockquote>
For my use case, some of the assumptions about addrspace(0) don't
make any sense, so having the option of not using it for stack
allocations would avoid some special case problems. For example,
it's assumed that 0 is the address space of code, and stack, but for
us these are unrelated concepts and have different pointer sizes.
The assumption that 0 is not a valid pointer value is also
incorrect, since we want stack pointers to be a 32-bit offset and 0
is valid. For this use case, all allocas should be created with the
same address space, so it could be part of the datalayout. In the
backend, we have 3 different memory types we would like to place
stack objects, so being able to mark these with different address
space IDs would also be helpful (although we wouldn't care about the
middle end deciding that some allocas should be in a different
address space from a single one specified by the data layout)<br>
</body>
</html>