[LLVMbugs] [Bug 18779] New: emmintrin.h uses __in as a parameter name that may conflict with code originally written for MSVC

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=18779

            Bug ID: 18779
           Summary: emmintrin.h uses __in as a parameter name that may
                    conflict with code originally written for MSVC
           Product: new-bugs
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: trivee at gmail.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

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.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa383701%28v=vs.85%29.aspx).
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 https://z3.codeplex.com/workitem/74. 

I suggest renaming this parameter to __a as is common in many other intrinsic
function definitions.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140209/dc36b893/attachment.html>