search for: unintrusively

Dear fellow CentOS users, for my few hobby projects (web games + forums) I have been using CentOS 5 (then 6) with Drupal and PostgreSQL plus few custom PHP and Perl scripts written by mysef. Since PostgreSQL version delivered with CentOS package has been a bit dated, I always used the PGDG packages: # rpm -qa | grep -i pgdg pgdg-centos93-9.3-1.noarch

Hello, I just subscribed to the list to join the discussion after being blindsided by the change and reading Dirk Eddelbuettel's reply to my bug report at https://bugs.debian.org/866768 . As far as I can tell the advantages of site library are: 1. Saves disk space and a little bit of user time spent installing and upgrading. 2. Other Debian package manages, like pip, default?to

Hi, > I have used such settings (such as un-setting R_LIBS_USER or its > predecessors) for over a decade, it just works (if you give write > permissions). It clearly helps us at work because everybody sees by > the default the same packages. I have also spoken with different R > Core members and several find the default installation below $HOME and > in a versioned directory

Hi, As comments are welcome I will give my two cents and a patch suggestion :-) 2017-07-06 10:42 GMT+02:00 Dirk Eddelbuettel <edd at debian.org>: > > > I have used such settings (such as un-setting R_LIBS_USER or its > predecessors) for over a decade, it just works (if you give write > permissions). It clearly helps us at work because everybody sees by > the default the

Hello, This patch implements cross-block dead store elimination for a simple scenario -- which was somehow important in my case --, i.e. when a store has only one memory dependence in a function. This patch is a bit narrow-minded (e..g, only store instructions are checked for memory dependencies), but I can always make it more generic, if you give me pointers *and* my code is correct. Cheers,

Hi Gianluca, did you look at Jakub Staszak's "Non-local DSE" patch he posted to the mailing list a while ago? Ciao, Duncan.

Pavel, Your tone does not exactly help in this discussion. Briefly, I (like many other people) consider Linux and Unix to be multi-user systems. You can argue as passionately for a default installation in /usr/loca/lib/R/site-library as you did against. And some of your arguments are just silly ("dangerous group": dude, it is one 'sudo addgroup r-adm' [or anotther name...])

On Thu, Jul 06, 2017 at 02:02:52PM +0200, Sergio Oller wrote: > Hi, > > As comments are welcome I will give my two cents and a patch suggestion :-) > > 2017-07-06 10:42 GMT+02:00 Dirk Eddelbuettel <edd at debian.org>: > > > > > > I have used such settings (such as un-setting R_LIBS_USER or its > > predecessors) for over a decade, it just works (if you

On Thu, Aug 24, 2017 at 6:30 PM, Justin Bogner <mail at justinbogner.com> wrote: > Peter Collingbourne <peter at pcc.me.uk> writes: > > On Thu, Aug 24, 2017 at 3:38 PM, Kostya Serebryany <kcc at google.com> > wrote: > > > >> > >> > >> On Thu, Aug 24, 2017 at 3:35 PM, Peter Collingbourne <peter at pcc.me.uk> > >> wrote:

Kostya Serebryany <kcc at google.com> writes: > Justin, > Calling appendToUsed has horrible complexity and if we call it in > every function clang consumes tons of memory (6Gb when compiling one > of the clang's source files). This killed my machine today :) > > The solution is to call appendToUsed once per module, instead of once > per function. Oh right,

On 7 July 2017 at 05:06, Dirk Eddelbuettel <edd at debian.org> wrote: > On Thu, Jul 06, 2017 at 02:02:52PM +0200, Sergio Oller wrote: > > Hi, > > > > As comments are welcome I will give my two cents and a patch suggestion > :-) > > > > 2017-07-06 10:42 GMT+02:00 Dirk Eddelbuettel <edd at debian.org>: > > > > > > > > > I

Hi all, >> In other words, the dhcp server has to start the client on the >> correct binary for it's arch and by virtue of running different bins, >> we can determine the most appropriate config file for the client? > > That is definitely one way to deal with it. > > There is no way around the fact that you have to have different binaries > for different

On Thu, Aug 24, 2017 at 3:38 PM, Kostya Serebryany <kcc at google.com> wrote: > > > On Thu, Aug 24, 2017 at 3:35 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> On Thu, Aug 24, 2017 at 3:21 PM, Kostya Serebryany via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> >>> >>> On Thu, Aug 24, 2017 at 3:20

Any idea why this calculates the integer the way it does? irb> ("291.15".to_f * 100.0).to_i => 29114 Thanks, Tom -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to

Changes since v3: - Use a single dma_attr for all DMA-API allocations in instmem instead of one per allocation - Use device.info.ram_size instead of pfb->ram to check whether VRAM is present outside of nvkm Changes since v2: - Cleaner changes for ltc - Fixed typos in gk20a instmem IOMMU comments Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into

Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into nouveau_display.c and nv84_fence.c. Original cover letter: Patches 1-3 make the presence of a RAM device optional, and remove GK20A's dummy RAM driver we were using so far. On chips using shared memory, such a device can confuse the driver into moving objects where there is no need to, and can trick

A series I have waited too long to submit, and the recent refactoring made me pay the price of my perfectionism, so here are the features that are at least completed Patches 1-3 make the presence of a RAM device optional, and remove GK20A's dummy RAM driver we were using so far. On chips using shared memory, such a device can confuse the driver into moving objects where there is no need to,

Thanks Ilia for the v2 review! Here is the v3 of this IOMMU support for GK20A series. Changes since v2: - Cleaner changes for ltc - Fixed typos in gk20a instmem IOMMU comments Changes since v1: - Add missing else condition in ltc - Remove extra flags that slipped into nouveau_display.c and nv84_fence.c. Original cover letter: Patches 1-3 make the presence of a RAM device optional, and remove