[Openmp-dev] iomp.h vs omp.h

[Peyton, Jonathan L]

Here is what I have so far for the name change patch.  It is successfully creating symlinks at install time and has renamed most of the libiomp stuff to libomp.

Concerning iomp.h, this header was first created to allow libgomp users to include Intel-specific features in their code while they used libgomp's omp.h file.  This way users could just add #include "iomp.h" to use exported kmp[c]_ functions.  It is not needed for the LLVM project.

-- Johnny

-----Original Message-----
From: Jack Howarth [mailto:howarth.mailing.lists at gmail.com] 
Sent: Friday, May 29, 2015 1:46 PM
To: Peyton, Jonathan L; openmp-dev at dcs-maillist2.engr.illinois.edu
Subject: iomp.h vs omp.h

Jonathan,
      I have been taking a stab at renaming libiomp5 to libomp locally and am puzzled by a header name conflict. Currently we have...

runtime/src/include/30/iomp.h.var
runtime/src/include/30/omp.h.var
runtime/src/include/30/iomp_lib.h.var
runtime/src/include/30/omp_lib.h.var
runtime/src/include/40/iomp.h.var
runtime/src/include/40/omp.h.var
runtime/src/include/40/iomp_lib.h.var
runtime/src/include/40/omp_lib.h.var
runtime/src/include/41/iomp.h.var
runtime/src/include/41/omp.h.var
runtime/src/include/41/iomp_lib.h.var
runtime/src/include/41/omp_lib.h.var

which will produce filename conflicts when eliminating the usage of iomp. What is the purpose of the headers prefixed with 'i'? Is this some legacy cruft from clang-omp which can be dropped as I don't seen any actual usage of the prefixed headers.
            Jack
-------------- next part --------------
A non-text attachment was scrubbed...
Name: name_change.patch
Type: application/octet-stream
Size: 12307 bytes
Desc: name_change.patch
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20150529/375d8f36/attachment.obj>