search for: cleanliness

Hi all Is there any compiler for R ? By compiler, I mean something that check the cleanliness of the code : if we declare all the variables we use, if we don't use external variable from a function and so on... For exemple, something that will ring a bell on the following code (saying "line 4 : 'pp' undefine in function 'power' ") 1. pp <- 3 2. power <...

Hi, The ldN like intrinsics (including all the ld1xN, ldN, ldNlane, ldNr, stN, stNlane) can use any pointer types. The definition (in IntrinsicsAArch64.td) of such intrinsics use 'LLVMAnyPointerType', which means we can pass any pointer type to such intrinsics. E.g. I tried following case ld2.ll: define { <4 x i32>, <4 x i32> } @test(float* %ptr) { %vld2 = call {

...already existing *current plot*. So plot your data (e.g. with plot(x, y)) before adding a regression line.” I interpreted the above to suggest the following --- plot(allEffects(Clean.label),ask=FALSE, alternating = TRUE, ylab="Probability of Rating", xlab="City",main="Cleanliness Ratings by City", factor.names=FALSE, ticks=c(0.1,0.2,0.3,0.4,0.5,0.6)) abline(h=c(0.1,0.2,0.3,0.4,0.5,0.6)) Error in int_abline(a = a, b = b, h = h, v = v, untf = untf, ...) : plot.new has not been called yet Less bothersome is the fact that the tick marks weren’t modified to 0.1, 0.2,...

...trying to filter out all of the words in a Term Document Matrix that are not in a list of words that I am interested in. I am using the following code: z<-tm_intersect(txt.dtm, c("communications", "safety", "climate", "blood", "surface", "cleanliness", "amenities", "monitoring", "staff", "competency", "policy", "procedure", "inconsistency", "physician", "orders", "treatment", "times", "care", "plan", "strat...

...39;t supposed to change. > > > Details are in the bug: https://llvm.org/bugs/show_bug.cgi?id=26226 > > > Any ideas? > > Not a huge fan of a ppc specific intrinsic (which it should be, so > llvm.ppc... if we go that route) to do this. I actually rather liked > the cleanliness of the address space solution for x86. How much work > would it be to do that? Alternately: Hal, Kit, what do you two think > as far as the ppc backend? > The other solution you mentioned - combining the slot load into the > existing intrinsic might work, we'd just need to figure o...

...ents directly, since no easy way to add an 8-bit-clean comment is provided by the current API. Anyway, either the spec or the code has to change. I hope it's the code, so I can make my totally unworthy t-shirt claim. And yah, I realize the comment tools don't handle the spec'ed 8-bit cleanliness yet either. Erik. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. U...

...; Details are in the bug: https://llvm.org/bugs/show_bug.cgi?id=26226 >>> >>> Any ideas? >>> >>> >> Not a huge fan of a ppc specific intrinsic (which it should be, so >> llvm.ppc... if we go that route) to do this. I actually rather liked the >> cleanliness of the address space solution for x86. How much work would it >> be to do that? Alternately: Hal, Kit, what do you two think as far as the >> ppc backend? >> >> The other solution you mentioned - combining the slot load into the >> existing intrinsic might work, we'...

...his old one. So I think it is actively in our best interest to not invest in changing #1. 3) LLVM (and its subprojects) have a long history of beneficially tracking and leveraging modern aspects of C++. We want to do more of this faster, not less of it slower, because it significantly improves the cleanliness, maintainability, simplicity, and performance of our libraries. To this end, it is directly to the benefit of the project to stay as close as possible to the latest versions of the various toolchain vendors. 4) Users of LLVM that are necessarily dealing with an unchanging toolchain and environment...

...bably isn't actually caring much for the performance of their target. Has the time come to start getting rid of the old SelectionDAG scheduler? I have no pressing *need* to do this, so if the answer is "no", fine. But if it's "yes", I'm willing to do my part for code cleanliness. (Eric said on IRC that sounded probably a reasonable thing to do but I should ask Andrew first; so cc'd.) I'd propose to do it in a few steps: Step 1: Switch defaults, and all in-tree targets away from selectiondag schedulers and to the machine scheduler. That is, 3 changes: a) Change...

I have table which stores multiple entries. Each row has user_id, game_id and a pick_id. On a page the user has to make load of choices. All this gets submitted. the html looks like so: <input type="hidden" name="game_id" value="3"> <input type="hidden" name="user_id" value="19"> <select name="pick[3]"> ....

When -fstack-protector is turned on, linker fails to find the symbol "__stack_chk_guard" because at least for powerpc64le, glibc doesn't provide this symbol. Instead, they put the stack guard into TCB. x86 fixed this issue by injecting a special address space (which is later translated to TCB register access) and hard code the offset of stack_guard, but I don't see a easy way to

Hi all. have fglrx driver working with xen, opengl runs fine for me. see http://pastebin.ca/350588 it''s tested with kernel 2.6.19, driver version 8.33.6, xen version 3.0.3 and 3.0.4 thanks to Jacob Gorm Hansen for suggestions testing, feedback (and bugreports - hope not) are welcome Christian -- "Without music to decorate it, time is just a bunch of boring production

-1. I believe there are still a lot of people using VC 2008, though I can't give the data. VC 2008 (even the express version) is enough for a lot of development, such like game development. Most likely I myself will continue using VC 2008 for at least two or more years. Unlike other C++ compiler, **Clang is not only a compiler, but also a great open source library**. An open source library

JonY wrote: > On 3/17/2013 23:01, LRN wrote: > >> All those ifdefs will at least be confined rather than spread out > >> through the code. > > I did it plibc-style: > > > > in compat.h: > > #if defined(_WIN32) > > #define FOPEN grabbag__fopen_utf8_wrapper > > #else > > #define FOPEN fopen > > #endif > > > > in

Hello, Michael Smith <msmith@xiph.org>: > > We don't sent a content-length header because there's no way to know the > content length in advance - it's a stream, after all! I kown this, after more than 1 hour the flash player stop to play. But during 1 hour It's possible to listen music, better than hearing nothing. > > So, I made a small PHP proxy and

I have over 12 sip trunks that are very similiar, like extension 412 below. Is there any way to have a single variable in [general] that contains the 7 lines after 'username=412'? This would reduce clutter in sip.conf. I don't want to put these common lines in [general]. What I have now repeated 12x: [412] username=412 context=default type=friend qualify=yes insecure=very

Samba users, I have compiled Samba 3.3.6 from the pristine sources on samba.org on a CentOS 5 machine. When I compiled Samba, CentOS's samba-common package was installed and specifying 'winbind' in /etc/nsswitch.conf allowed winbind to supply user information. For the sake of cleanliness and removing old libraries, I removed the samba-common package. Now, specifying 'winbind' in nsswitch.conf does nothing. What I mean exactly is that using `id domain_user` or `id MYDOMAIN+domain_user` both return "no such user." I can't authenticate as any users that winbi...

...letions(-) Ok, I like it after all. Mind changing over arch/x86/kprobes/* to use this new facility? There's no sense in kprobes internals using two types After that we can convert all the rest, probably as part of this series. There's a good reason now to do it: it's not just about cleanliness, it will also impact generated code less. Thanks, Ingo

...L1_CACHE_SIZE)), we could encode the truesize in the least significant 8 bits of the buffer address (encoded as truesize >> 8 as we know all sizes are a multiple of 256). This would allow packet buffers up to 64KB in length. Is there another approach you would prefer to any of these? If the cleanliness issues and larger alignment aren't too bad, I think (2) sounds promising and allow us to eliminate the metadata ring entirely while still permitting RX frag coalescing. Best, Mike

...1 > > Yep, I prefer not to have too much #ifdef hackery. > > In my recent replacement of all the sprintf/_snprintf stuff, I relaced all > the > calls with a call to flac_snprintf() and localised #ifdef hackery to the > implementation of that function. > > >From a patch cleanliness POV, I like to see the new functionality added in > one patch and a separate patch to change all the old function usage to the > new function usage. For example, in commit 06af237c I added the new > flac_snprintf() function and in commit 3c84f9e8 I replaced all the old > calls to sprint...