search for: burdensome

...ites silent coding errors. I did this because I have to propagate the non-temporal information through various phases of lowering and making these non-default helps me catch missing cases. We've done the same in our local sources and we've never found specifying the extra arguments to be burdensome. -Dave

Hi, I need to run a burdensome simulation. I'm using a Dell PowerEdge 2850, 3.8 Ghz CPU, 2 Gb RAM, Windows server 2003, 32 bit. The task manager indicates that Rgui.exe is using 25% of the CPU speed. There is no other process that is slowing down R. Does anyone know if it's a limitation of R? If so, can I set up the pr...

...rs. I did this because I have to propagate the non-temporal > information through various phases of lowering and making these non-default > helps me catch missing cases. > > We've done the same in our local sources and we've never found > specifying the extra arguments to be burdensome. I have a patch ready to track nontemporal semantics but I'm waiting for an opinion on this. I'd really like to get this integrated for 2.7. In my opinion default arguments are a bad idea in this context. It's very easy to make coding errors. I found a couple more today. Thanks....

All, I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually...

Hello, Currently if you install a package twice: install.packages("testit") install.packages("testit") R will build the package from source (depending on what OS you're using) twice by default. This becomes especially burdensome when people are using big packages (i.e. lots of depends) and someone has a script with: install.packages("tidyverse") ... ... later on down the script ... install.packages("dplyr") In this case, "dplyr" is part of the tidyverse and will install twice. As the primary...

...use unique_ptr for ownership. Many of which remove uses of explicit delete or helpers like DeleteContainerPointers (and removing explicit dtors in many of those cases). Are people OK with/prefer the use of owning smart pointers in APIs? Are there places where you've found them to be too noisy/burdensome and would rather use raw pointers or some other abstraction? Would you prefer pre-commit review of such changes to adequately consider alternatives (such as?)? Thanks, - David

...> Currently if you install a package twice: > > > > install.packages("testit") > > install.packages("testit") > > > > R will build the package from source (depending on what OS you're using) > > twice by default. This becomes especially burdensome when people are > using > > big packages (i.e. lots of depends) and someone has a script with: > > > > install.packages("tidyverse") > > ... > > ... later on down the script > > ... > > install.packages("dplyr") > > > > In...

...ture of Phabricator: if you look at a file in blame mode, there are little "<<" next to the revision, which lets you jump to the file "past that revision". This lets one quickly browse to the right point for what one is looking for, making naming or formatting changes less burdensome. Example: http://reviews.llvm.org/diffusion/L/browse/cfe/trunk/include/clang/Basic/DiagnosticIDs.h;198376 Cheers, /Manuel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141008/fd68d692/attachment.html>

...ling to be the code owner for the llgo subproject. The frontend would live in the LLVM svn repository and if checked out into tools/llgo would build as part of the regular LLVM build (with CMake only). We would be keeping llgo compatible with top-of-tree LLVM, although I imagine this would be less burdensome than the other subprojects as llgo is written in Go and depends on the Go bindings previously contributed to LLVM. llgo depends on certain third-party components, namely a copy of the Go standard library (libgo), a Go program analysis library (go.tools) and two library dependencies of the standard...

...a file in blame mode, >> there are little "<<" next to the revision, which lets you jump to the file >> "past that revision". This lets one quickly browse to the right point for >> what one is looking for, making naming or formatting changes less >> burdensome. >> Example: >> http://reviews.llvm.org/diffusion/L/browse/cfe/trunk/include/clang/Basic/DiagnosticIDs.h;198376 >> > > > That is really great! I need this from time to time and though it's not > difficult to approximate on the command line, it is tedious. This sa...

...rosier at apple.com> wrote: > All, > I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually...

...lues in the trainset vs. 4 different ones in the testSet. I am not sure if this is the cause.If so, what would be the remedy? Since I can retrieve the coefficients of the logistic regression, I could manually calculate response for each entry in the testSet. This could solve my problem although burdensome. But, I don't know an easy way of doing it as my logistic regression have 80+ coefficients. Could somebody advise? Thanks, M [[alternative HTML version deleted]]

...upport %u or %h in ForceCommand :( I am using command="rsync --server --daemon ." in ~/ssh/authorized_keys. Correct me if I'm wrong, but I believe this eliminates the need for %u or %h and ForceCommand. It does mean that key based authentication is required, but this does not seem burdensome for a backup oriented solution. Karl <kop at meme.com> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein

Oh, one thing I forgot to mention: ReadOnly objects are also counted as small data globals on PPC (on top of BSS, Data, Common). That's what the r2 base is for (.sdata2, defined to be constant data). 32-bit immediate loads take 2 ops minimum on PPC, so even constant loading benefits from small data. It'd be handy to add a third argument containing what kind would normally be returned:

...(5.2607), Ratio_sum (1.29985), Ratio_min (2.1533), Ratio_max (11.1469). But I would like to have the results just at once, in one column or one after the other (and not to run the code for every single result). I do have almost 200 columns that start with Ratio_, so doing it by hand it's really burdensome... I tried with a "for" loop: for (x in 1:5) { x <- with(data, c(Ratio_mean, Ratio_median, Ratio_sum, Ratio_max, Ratio_min)) Mean <- with(data mean(x)) print(Mean) } But the result is: [1] 4.66979 [1] 4.66979 [1] 4.66979 [1] 4.66979 [1] 4.66979 which is the mean of a...

+the people I hashed this out with so many months ago I think it's a reasonable proposal, but obviously I floated it. :) Let's try to get a second opinion. Again, it's a syntax something like: define void @foo() prefix [i8* x 2] { i8* @a, i8* @b } prologue [i8 x 4] c"\xde\xad\xbe\xef" { ret void } On Thu, Aug 21, 2014 at 1:58 PM, Ben Gamari <bgamari.foss at

...t apple.com> wrote: >> All, >> I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually...

...nsole file without problem. But if I bring up the GUI preferences (from menus Edit | Gui Preferences), only TT fixed width fonts are shown, the "font" field is blank, and ending that dialog results in the font being reset to the default fixed system font. If practical and not overly burdensome to fix that, it would be nice. (3) Could the toolbar could be available on the main window even under SDI? I much prefer SDI, which doesn't waste vast amounts of screen space like MDI, but the toolbar can be handy. (4) Any chance of binding the F-keys to things like ls(), ls.str(), or ma...

...nsole file without problem. But if I bring up the GUI preferences (from menus Edit | Gui Preferences), only TT fixed width fonts are shown, the "font" field is blank, and ending that dialog results in the font being reset to the default fixed system font. If practical and not overly burdensome to fix that, it would be nice. (3) Could the toolbar could be available on the main window even under SDI? I much prefer SDI, which doesn't waste vast amounts of screen space like MDI, but the toolbar can be handy. (4) Any chance of binding the F-keys to things like ls(), ls.str(), or ma...

...allow the AnalysisManager to walk the >> transitive dependencies). >> > > I think this is the right approach. I would personally start by overriding > the invalidate callback everywhere that it is necessary, and see how bad > that becomes. > > If it becomes common and burdensome, then we can change the way > invalidation works such that the analysis manager is aware of the preserved > analysis set in more detail, and have it build up the necessary data > structures to know in-advance whether it must make an explicit invalidate > call. > > However, I suspe...