<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 03/07/2014 01:28 PM, Chandler
Carruth wrote:<br>
</div>
<blockquote
cite="mid:CAGCO0Kg7pmgtgzNz1y2PNfvE5Qj7Mw=g4FpNOZEPCYKC9LGNSQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Mar 7, 2014 at 1:21 PM,
Michele Scandale <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:michele.scandale@gmail.com" target="_blank">michele.scandale@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">So you
suggest to allow bitcast between pointer of different
address spaces but with the same size. Is is correct?</blockquote>
</div>
<br>
Yes, that is part of my suggestion, but not all of it (see the
second part of the original mail).</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">However, we shouldn't do that without
confirming with others that this works. Adding Owen to the
CC-list.</div>
</div>
<br>
</blockquote>
<br>
I think it makes sense, although it will make it a bit harder to
find the most common address space bugs. Disallowing bitcasts
between address spaces also removed some questions about what to do
with casts involving address spaces when there was no datalayout,
but I guess that soon won't be a problem anymore.<br>
</body>
</html>