Joerg Sonnenberger
2015-May-02 23:09 UTC
[LLVMdev] [cfe-dev] libiomp, not libgomp as default library linked with -fopenmp
On Sat, May 02, 2015 at 11:18:35PM +0300, Andrey Bokhanko wrote:> 3) Some people believe that libiomp is not a proper name anymore and > should be changed. I'm not a library expert, so really don't know. > However, this means that we should flip default library setting ASAP. > Why? Because now "libiomp5" is a user-visible name (one has to use > "-fopenmp=libiomp5" to enable OpenMP in clang) and the sooner it will > become non user-visible, the better. Any objections here?Switch the library name together with the default value for clang. That seems like to the way forward. It doesn't break existing users, since they would still be using -fopenmp=libiomp5 and it doesn't introduce a surprise for new users after the lib name change. Joerg
Andrey Bokhanko
2015-May-03 06:50 UTC
[LLVMdev] [cfe-dev] libiomp, not libgomp as default library linked with -fopenmp
On Sun, May 3, 2015 at 2:09 AM, Joerg Sonnenberger <joerg at britannica.bec.de> wrote:> Switch the library name together with the default value for clang. That > seems like to the way forward. It doesn't break existing users, since > they would still be using -fopenmp=libiomp5 and it doesn't introduce a > surprise for new users after the lib name change.Joerg, I don't quite understand you. How switching library name won't break existing users that still use "-fopenmp=libiomp5"? After "libiomp5" will be renamed to, say, "superlib", "-fopenmp=libiomp5" won't be recognized anymore. Andrey
Joerg Sonnenberger
2015-May-03 12:12 UTC
[LLVMdev] [cfe-dev] libiomp, not libgomp as default library linked with -fopenmp
On Sun, May 03, 2015 at 09:50:18AM +0300, Andrey Bokhanko wrote:> On Sun, May 3, 2015 at 2:09 AM, Joerg Sonnenberger > <joerg at britannica.bec.de> wrote: > > Switch the library name together with the default value for clang. That > > seems like to the way forward. It doesn't break existing users, since > > they would still be using -fopenmp=libiomp5 and it doesn't introduce a > > surprise for new users after the lib name change. > > Joerg, I don't quite understand you. How switching library name won't > break existing users that still use "-fopenmp=libiomp5"? After > "libiomp5" will be renamed to, say, "superlib", "-fopenmp=libiomp5" > won't be recognized anymore.They can still use the old library? Joerg