search for: agreeable

...nd am trying to extract the factors of a dataframe using numeric indices (e.g. df[1]) that are input to a function definition instead of the other types of references (e.g. df$out). df[1] is a list(?) whose class is "dataframe". These indexed lists can be printed successfuly but are not agreeable to the plot() and lm() functions shown below as are their df$out references. Reading the documentation for plot and lm hasn't helped yet. Thanks in advance - Stan. > df=data.frame(out=1:4*3,pred1=1:4,pred2=1:4*2) > regression=function(tble,a,b) + { + plot.new() +...

...ugacha at gmail.com> wrote: > Which brings us to my fallback proposal: what about disabling the > pass on darwin only? That's a decision for Jim/Evan. I'm ok if they are. > As for other targets, as a first step, making the pass run under -O3 > rather than -O1 is hopefully agreeable to everyone? Sounds reasonable. Even though it conflicts with LTO, that's what O3 means, as you said, instability. People at O3 might want to fiddle with the passes (on/off) to get the best performance for their own code/workload. cheers, --renato

...w > I'm pretty packed with travel in August already, only some of which is > going to be directly sponsored or endorsed by work. Everything else > will have to be out of my personal time budget. I'd actually prefer > something *later*, like September, but that's probably not agreeable > to others. Maybe early-ish July instead? > Hi Dan, As far as I know, a date hasn't been set yet. I personally don't have a preference, but then again I don't travel much. :-) -bw

...brings us to my fallback proposal: what about disabling the >> pass on darwin only? > > That's a decision for Jim/Evan. I'm ok if they are. Jim, thoughts? > >> As for other targets, as a first step, making the pass run under -O3 >> rather than -O1 is hopefully agreeable to everyone? > > Sounds reasonable. Great! > Even though it conflicts with LTO, that's what O3 means, as you said, > instability. People at O3 might want to fiddle with the passes > (on/off) to get the best performance for their own code/workload. By the way, I'm not convi...

...y.newcastle.edu.au/R/e11/help/10/09/9865.html. For example, this code using xyplot produces a logged y-axis but the labels (e.g. "10^1.2") are not very user-friendly: xyplot(24:300~24:300, scales=list(y=list(log=T))) So, trying another y.scale.component function, we get something more agreeable for y-axis scale labels: xyplot(24:300~24:300, scales=list(y=list(log=T)), yscale.components = yscale.components.log10.3) However, my problem is that occasionally I'll have to plot data that doesn't quite "work". For example, in the following example, I only get one y-axis sca...

...mitigate the adrp problem, and global usage is usually frowned upon in those circles (except for singletons, class-/function-statics and whatnot, which I'm trying to address in an upcoming patch). As for other targets, as a first step, making the pass run under -O3 rather than -O1 is hopefully agreeable to everyone? After all, it is "aggressive", and isn't always profitable. That's pretty much the description of -O3. We can still run into problematic cases under LTO, though. -Ahmed > > Thanks, > > Kristof > > > -----Original Message----- > > From: l...

I've been using (and loving) R for quite a while now, but I have to admit that something simple is still stumping me. The question is how I can control the box within which a plot is drawn, in cases where I'm controlling the aspect ratio with the "asp" argument. The problem comes up in pdf() and png() output formats, but also with interactive windows, and so I'll

...Clang, Compiler-RT, Clang-Tools-Extra, LibCXX, LibCXXABI and > Test-Suite repos > >> > >> During the week of 4/30 I will revert as necessary if bots fail. > Hopefully having the change permanently landed by the middle of the week. > >> > >> Does this sound agreeable to everyone? > > > > I'd like to propose a different approach. How about we do this the > > other way around? Maybe we should try the "move first, fix later", > > than the "break first, despair later". > > > > This week we (Linaro) have fi...

...ess in an upcoming patch). > > Before making the disabling darwin only I'd like to see some analysis of the regressions/improvements. Has anyone looked at the code for those yet? > As for other targets, as a first step, making the pass run under -O3 > rather than -O1 is hopefully agreeable to everyone? After all, it is > "aggressive", and isn't always profitable. That's pretty much the > description of -O3. > We can still run into problematic cases under LTO, though. > > Seems reasonable to me, but probably want to see what happens with the above qu...

> On Apr 27, 2016, at 11:17 AM, Renato Golin <renato.golin at linaro.org> wrote: > > On 27 April 2016 at 18:41, Chris Bieneman <beanz at apple.com> wrote: >> Renato, in your most recent email you comment about differentiating *stable* vs random versions of CMake built from source. I believe as a community our recommendation should be that people download CMake sources

...ht mitigate some of the potential issues should one of the RPI3s fail. A better idea, which I had not thought of until your message, would be to run a Debian or Ubuntu virtual machine on the Dell R710 and install the AD there. Then I could directly use Louis's packages. This option is very agreeable. -- Paul (ganci at nurdog.com) Cell: (303)257-5208

...here this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms... My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150529/e40c57f3/attachment.html>

...nly I'd like to see some analysis of the > regressions/improvements. Has anyone looked at the code for those yet? Yep, I put a quick analysis in my other reply. > >> >> As for other targets, as a first step, making the pass run under -O3 >> rather than -O1 is hopefully agreeable to everyone? After all, it is >> "aggressive", and isn't always profitable. That's pretty much the >> description of -O3. >> We can still run into problematic cases under LTO, though. >> > > Seems reasonable to me, but probably want to see what happ...

...order of the RemoteForward requests, eg. SSH_REMOTE_FORWARD_PORT_1, SSH_REMOTE_FORWARD_PORT_2, .... I was able to wedge a proof of concept into session.c:do_setup_env (patch below). It's a hack because there doesn't seem to be an API to iterate channels outside of channels.c. Would it be agreeable to export channels and channels_alloc? Also, struct Channel doesn't let you tell which forwards were dynamically allocated, so an environment variable is set for all RemoteForwards. This could be changed by extending struct Channel, though it isn't a show-stopper for me. Last thought: if...

...ns/improvements. Has anyone looked at the code for those yet? > > Yep, I put a quick analysis in my other reply. > The LOH/ADRP bit? > > > > >> > >> As for other targets, as a first step, making the pass run under -O3 > >> rather than -O1 is hopefully agreeable to everyone? After all, it is > >> "aggressive", and isn't always profitable. That's pretty much the > >> description of -O3. > >> We can still run into problematic cases under LTO, though. > >> > > > > Seems reasonable to me, but...

...k the version in devel is currently unusable, and has far, far too many conflicts. Given Paul's claims of stability, I have spent a deeply frustrating afternoon. timeslab ======== Rather self-contained, copyright position unclear (to me). Suggestions: =========== If Martyn and Adrian are agreeable, I will start a library(ts) in the 0.65 version. I will put in this: the ts class and methods (maybe in due course these should be removed from the base package?) datasets from MASS, tseries lag, deltat, cycle filter acf from bats, augmented by ideas from tseries. spectrum, spec.pgram from bat...

...where this information could be stored (it's similar to what's stored in the WinEHFuncInfos hanging off the MMI today). But adding hooks for client passes might be opening a can of worms… My inclination would be #2 or #3, but I would love some feedback on which of the tradeoffs seem most agreeable (and/or what options I've overlooked). Thanks -Joseph _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu<mailto:LLVMdev at cs.uiuc.edu> http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- nex...

Hi Ahmed, Did you run these experiments on a platform with a linker that makes use of the AArch64CollectLOH-pass-produced information? I'm guessing that the AArch64CollectLOH-pass information and a linker that makes use of that information could affect the profitability of the GlobalMerge pass? Thanks, Kristof > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu

...tored (it's similar to what's stored in the WinEHFuncInfos hanging off the > MMI today). But adding hooks for client passes might be opening a can of > worms… > > > > My inclination would be #2 or #3, but I would love some feedback on which > of the tradeoffs seem most agreeable (and/or what options I've overlooked). > > > > Thanks > > -Joseph > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/ll...

.... Note how many ifdefs were needed to work with all versions from 3.1 to now. If this were added to the LLVM project it could be maintained in one place with no ifdefs. If the LLVM maintainers don't want it, I also have a patch to allow subclassing DefaultJITMemory manager. Would that be more agreeable? Thanks. class DelegatingJITMemoryManager : public llvm::JITMemoryManager { protected: virtual llvm::JITMemoryManager *mgr() const = 0; public: /* * From JITMemoryManager */ virtual void setMemoryWritable() { return mgr()->setMemoryWritable();...