<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - emmintrin.h uses __in as a parameter name that may conflict with code originally written for MSVC"
href="http://llvm.org/bugs/show_bug.cgi?id=18779">18779</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>emmintrin.h uses __in as a parameter name that may conflict with code originally written for MSVC
</td>
</tr>
<tr>
<th>Product</th>
<td>new-bugs
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>new bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>trivee@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>emmintrin.h uses __in as a name for the input parameter in several functions
(_mm_castpd_ps etc)
At the same time, Microsoft uses __in as a parameter annotation for static
analysis (see e.g.
<a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa383701%28v=vs.85%29.aspx">http://msdn.microsoft.com/en-us/library/windows/desktop/aa383701%28v=vs.85%29.aspx</a>).
It is relatively common to define __in to be an empty macro when compiling code
originally developed with MSVC on other compilers.
The combination of these two may lead to puzzling problems - see e.g. the
discussion in <a href="https://z3.codeplex.com/workitem/74">https://z3.codeplex.com/workitem/74</a>.
I suggest renaming this parameter to __a as is common in many other intrinsic
function definitions.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>