search for: common_

...std=c++98" in Makevars | anyway, even if it's just to avoid users using C++11 constructs and then | wondering why their packages fail on CRAN? There is still no minimally preproducible example here; just a (pardon me here) rambling description of a hasty system upgrade. It is _somewhat common_ to have to recompile C++ shared objects when compiler major versions change. So I am unsure if we have actually demonstrated a bug here. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

...even if it's just to avoid users using C++11 constructs and then | > | wondering why their packages fail on CRAN? | > | > There is still no minimally preproducible example here; just a (pardon me | > here) rambling description of a hasty system upgrade. | > | > It is _somewhat common_ to have to recompile C++ shared objects when compiler | > major versions change. | > | > So I am unsure if we have actually demonstrated a bug here. | Don't we need "-std=c++98" for GCC 6 in Makevars anyway, even if it's | just to save users from using C++11 constructs a...

...; | anyway, even if it's just to avoid users using C++11 constructs and then > | wondering why their packages fail on CRAN? > > There is still no minimally preproducible example here; just a (pardon me > here) rambling description of a hasty system upgrade. > > It is _somewhat common_ to have to recompile C++ shared objects when compiler > major versions change. > > So I am unsure if we have actually demonstrated a bug here. Don't we need "-std=c++98" for GCC 6 in Makevars anyway, even if it's just to save users from using C++11 constructs and then wo...

...ies to check for stream errors by comparing to NULL or 0": if (file != NULL) > | > > | > There is still no minimally preproducible example here; just a (pardon > me > | > here) rambling description of a hasty system upgrade. > | > > | > It is _somewhat common_ to have to recompile C++ shared objects when > compiler > | > major versions change. > | > > | > So I am unsure if we have actually demonstrated a bug here. > | Don't we need "-std=c++98" for GCC 6 in Makevars anyway, even if it's > | just to save users...

On 12 November 2016 at 07:59, Dirk Eddelbuettel wrote: | | On 12 November 2016 at 14:23, Kirill M?ller wrote: | | Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's | | picked up properly. I can only assume that the last -std= option wins if | | more than one are given on the same command line [1]. | | Good to know it works. | | I am still a little puzzled why it was

Dear Rexperts, lately I'm having troubles installing the rgl package via install.packages("rgl", dependencies=T) in the R 2.4.0 backport running under Ubuntu 6.06 LTS. I get the following error messages, despite having installed libx11-dev (as recommended in a similar post about SUSE 10.1): trying URL 'http://cran.xedio.de/src/contrib/rgl_0.68.tar.gz' Content type

...nLDAP proxy > documentation from the Wiki. > > > > 3.) If you don't want/need to move to Samba AD, then simply upgrade as > usual and continue running Samba as NT4 PDC. Samba 4 doesn't require to > migrate to AD: > > https://wiki.samba.org/index.php/Updating_Samba#Common_misconceptions_about_Samba_4 > > > > If this doesn't answer you question, then please give a comprehensive > overview about your current setup, the setup you plan to get and about > your environment. This would make it easier to help, instead of > guessing. ;-) > > &gt...

...gt;> >>> >>> 3.) If you don't want/need to move to Samba AD, then simply upgrade as >>> usual and continue running Samba as NT4 PDC. Samba 4 doesn't require to >>> migrate to AD: >>> >>> https://wiki.samba.org/index.php/Updating_Samba#Common_ >>> misconceptions_about_Samba_4 >>> >>> >>> >>> If this doesn't answer you question, then please give a comprehensive >>> overview about your current setup, the setup you plan to get and about >>> your environment. This would make...

...common one but still generally make use of the improvements made by the wider community. This is where GICombinerGroup will start to shine as such a target can declare a combiner like so: def MyTargetPreLegalizerCombiner: GICombiner< "MyTargetGenPreLegalizerCombiner", [common_extend_optimizations, common_extending_loads, // common_rsqrt_and_nr_iterations, // This target has a real sqrt operation mytarget_special_fma, common_fma, common_bswap_idioms, mytarget_bcd_arithmetic ]> { } As LLVM improves on the common_* grou...

...ally make use of the improvements made by the wider community. This is where GICombinerGroup will start to shine as such a target can declare a combiner like so: >> def MyTargetPreLegalizerCombiner: GICombiner< >> "MyTargetGenPreLegalizerCombiner", >> [common_extend_optimizations, >> common_extending_loads, >> // common_rsqrt_and_nr_iterations, // This target has a real sqrt operation >> mytarget_special_fma, >> common_fma, >> common_bswap_idioms, >> mytarget_bcd_arithmetic &gt...

...of the improvements made by the wider community. This is where GICombinerGroup will start to shine as such a target can declare a combiner like so: >>>> def MyTargetPreLegalizerCombiner: GICombiner< >>>> "MyTargetGenPreLegalizerCombiner", >>>> [common_extend_optimizations, >>>> common_extending_loads, >>>> // common_rsqrt_and_nr_iterations, // This target has a real sqrt operation >>>> mytarget_special_fma, >>>> common_fma, >>>> common_bswap_idioms, &gt...