search for: linkin

...s particular machine (dual P3-866 Xeon with 2GB RDRAM). Regards, Andy > -----Original Message----- > From: Thomas Lumley [mailto:tlumley at u.washington.edu] > Sent: Friday, January 11, 2002 2:42 PM > To: Liaw, Andy > Cc: 'r-help at stat.math.ethz.ch' > Subject: Re: [R] linking R against MKL > > > On Fri, 11 Jan 2002, Liaw, Andy wrote: > > Also, has anyone compared MKL with ATLAS? Maybe it's not > worth the effort > > fooling with MKL? > > There's some discusssion on the math-atlas-results list at the ATLAS > sourceforge page...

...I actually managed to bootstrap llvm and clang itself. It didn't run very well though as you can imagine based on the above tests. It's not a performance issue but a code maintenance issue. The initial > patches to support mingw was trying to add a new linker driver and a > different linkin semantics to the COFF linker which seemed too complicated > to me. IIRC, I suggested adding a shim which translates GNU command line > arguments to MSVC linker arguments. Didn't it work? There were just so many differences between link and ld I never followed down that path. I pushed for...

...lf. >> It didn't run very well though as you can imagine based on the above >> tests. >> >> It's not a performance issue but a code maintenance issue. The initial >>> patches to support mingw was trying to add a new linker driver and a >>> different linkin semantics to the COFF linker which seemed too complicated >>> to me. IIRC, I suggested adding a shim which translates GNU command line >>> arguments to MSVC linker arguments. Didn't it work? >> >> There were just so many differences between link and ld I never foll...

...though as you can imagine based on the above >>>> tests. >>>> >>>> It's not a performance issue but a code maintenance issue. The initial >>>>> patches to support mingw was trying to add a new linker driver and a >>>>> different linkin semantics to the COFF linker which seemed too complicated >>>>> to me. IIRC, I suggested adding a shim which translates GNU command line >>>>> arguments to MSVC linker arguments. Didn't it work? >>>> >>>> There were just so many differences...

...above >>>>>> tests. >>>>>> >>>>>> It's not a performance issue but a code maintenance issue. The >>>>>>> initial patches to support mingw was trying to add a new linker driver and >>>>>>> a different linkin semantics to the COFF linker which seemed too >>>>>>> complicated to me. IIRC, I suggested adding a shim which translates GNU >>>>>>> command line arguments to MSVC linker arguments. Didn't it work? >>>>>> >>>>>> Ther...

...ests. >>>>>>>> >>>>>>>> It's not a performance issue but a code maintenance issue. The >>>>>>>>> initial patches to support mingw was trying to add a new linker driver and >>>>>>>>> a different linkin semantics to the COFF linker which seemed too >>>>>>>>> complicated to me. IIRC, I suggested adding a shim which translates GNU >>>>>>>>> command line arguments to MSVC linker arguments. Didn't it work? >>>>>>>> >&...

...to > bootstrap llvm and clang itself. > It didn't run very well though as you can imagine based on the above tests. > > It's not a performance issue but a code maintenance issue. The initial > patches to support mingw was trying to add a new linker driver and a > different linkin semantics to the COFF linker which seemed too complicated > to me. IIRC, I suggested adding a shim which translates GNU command line > arguments to MSVC linker arguments. Didn't it work? > > There were just so many differences between link and ld I never followed > down that path...

...to > bootstrap llvm and clang itself. > It didn't run very well though as you can imagine based on the above tests. > > It's not a performance issue but a code maintenance issue. The initial > patches to support mingw was trying to add a new linker driver and a > different linkin semantics to the COFF linker which seemed too complicated > to me. IIRC, I suggested adding a shim which translates GNU command line > arguments to MSVC linker arguments. Didn't it work? > > There were just so many differences between link and ld I never followed > down that path...

Hey llvm'ers, I have been working on a dlltool replacement for llvm. Here is my initial differential https://reviews.llvm.org/D29892 It is based on some functionality that already exists in lld. I added functionality to support, PE COFF Weak Externals and of course a front end to actually use it. I believe the work here can also be used for llvm-lib and lessen the load on lld. I would like

...to > bootstrap llvm and clang itself. > It didn't run very well though as you can imagine based on the above tests. > > It's not a performance issue but a code maintenance issue. The initial > patches to support mingw was trying to add a new linker driver and a > different linkin semantics to the COFF linker which seemed too complicated > to me. IIRC, I suggested adding a shim which translates GNU command line > arguments to MSVC linker arguments. Didn't it work? > > There were just so many differences between link and ld I never followed > down that path...

...grateful 4 somebody who can give me a good solution for this. -- Name : Arie Kusuma Atmaja, A.K.A Arie, A.K.A ariekeren / YM! = riyari3 http://ariekusumaatmaja.wordpress.com Let''s build Ruby Indonesia stronger http://groups.yahoo.com/groups/id-ruby Go go go Ruby go! Mp3Info.open("Linkin\ Park\ -\ Abyss.mp3") { |f| puts f }

...64, Version 16.0.1.150 Compiling : icc -std=gnu99 -I../../../../include -DNDEBUG -I../../../include -I../../../../src/include -DHAVE_CONFIG_H -I/usr/local/include -fpic -g -O2 -std=c99 -c fork.c -o fork.o icc: command line warning #10121: overriding '-std=gnu99' with '-std=c99' Linkin' : icc -std=gnu99 -shared -L/usr/local/lib64 -o parallel.so init.o rngstream.o fork.o Running : mclapply's simple example under R-3.2.5 Thank you for advice or discussion. Kind regards, Harold Petithomme ********************************************************* Harold PETITHOMME Equipe...

This is the situation I have: All my hosts are the* same OS.* All my host are in the* same puppet environment,* so I cannot use %{environment} I have a module that sets all the *basic* functionality for the OS, resolution, authentication, security, packages, etc I have a module for each application hosted. At the moment all the ''data'' is in Puppet, mostly in parametrised