search for: conflated

Hi, I think this is a pretty basic question. I still couldn#t find the answer to it, though. I have some data loaded into R, which looks like this: > data() ... 38358 Advice Article 38359 Advice Article 38360 GeneralInfo List 38361 GeneralInfo Article 38362 Purchase Paragraphs 38363 Purchase List 38364 Purchase Paragraphs ... I now

On 19 July 2016 at 23:16, Mehdi Amini <mehdi.amini at apple.com> wrote: >> In the past, we were hit by web spiders that ignored completely the >> robots.txt file. Anton has made that better, but it can escalate if >> the spider realise we blocked them. There are ways to work around, but >> not without accidentally blocking innocent people (mostly in China). > >

Perhaps it helps to know that I have access to the machines and have helped debug many of the current problems. I'm not speaking from the outside, guessing how hard things are. I also think you are assuming a lot about where services can be hosted and at which cost (labour, not hardware). So, unless you are volunteering to take care of the whole infrastructure, I suggest taking the opinion

Hi Jonathan, This looks a bit odd. Any reason for the unknown->none conflating in this way? For most (all) of the ports unknown-elf works the same as none-elf. I'm also not sure if someone decided to have, arm-codesourcery-elf that this would still work with the patch. Thoughts? -eric On Tue, Jun 24, 2014 at 7:35 AM, Amara Emerson <amara.emerson at gmail.com> wrote: > Hi Jon,

On 14 August 2014 11:26, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > So you don't want to send it to the standard output. The things that want to parse it expect a file in the filesystem. So if you want the verbose build to be sticking it in a well-known file then I don't have strong objections, but it seems to be conflating two things. We run lit in -q mode in

...nfigured) by WriterOptionsELF. The driver's job is to produce the right > WriteOptionsELF settings. For library based linking (no command line) > you just just code to instantiate an appropriate WriteOptionsELF. Interesting. As you have pointed out, currently the format and the os are conflated. Would it make sense to have Reader/Writer literally be concerned *only* with turning an atom graph into an output object file in a specific format? (each format may have format-specific atoms). Then the OS layer (+ architecture?) is implemented in a separate library that is a client of Reader/Writ...

I've been working on an R performance academic project for the last couple years which has involved writing an interpreter for R from scratch and a JIT for R vector operations. With the recent comments on Julia, I thought I'd share some thoughts from my experience since they differ substantially from the common speculation on R performance. I went into the project thinking that R would

Hi Jonathan, The main issue with your patch is that it can change user expected behaviour, and I can't tell you what is the expected behaviour in Darwin or BSD. If people usually use "unknown" in triples, this will break their builds. If not, this could break the build of someone who does. My advice is to create a "default" mechanism for the affected targets, something

Does anyone know if xapian stemming support suffix -er? I tried -s and -ing both work, but not -er. _________________________________________________________________ ?????????????? MSN Messenger: http://messenger.msn.com/cn

...onsELF. The driver's job is to produce the right >> WriteOptionsELF settings. For library based linking (no command line) >> you just just code to instantiate an appropriate WriteOptionsELF. > > Interesting. As you have pointed out, currently the format and the os > are conflated. Would it make sense to have Reader/Writer literally be > concerned *only* with turning an atom graph into an output object file > in a specific format? (each format may have format-specific atoms). > Then the OS layer (+ architecture?) is implemented in a separate > library that is a c...

Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. I will continue to look into the issue with the methods Tomas mentioned. Many thanks. On 2020-08-21 21:05:51 nospam at altfeld-im.de wrote: > May be unrelated but on SO there is a report that a Windows update may > cause this problem: > &...

On 5 Aug 2014, at 21:17, Filip Pizlo <fpizlo at apple.com> wrote: > - Engage with non-WebKit embedders that currently use the C++ API to figure out what it would take to get them to switch to the C API. I maintain a reasonable amount of out-of-tree code that embeds LLVM in various things, including a couple of language front ends, an out-of-tree back end, and some tools for interfacing

On 6/23/14, 8:31 AM, David Chisnall wrote: > On 23 Jun 2014, at 15:13, Renato Golin <renato.golin at linaro.org> wrote: > >> The main issue with your patch is that it can change user expected >> behaviour, and I can't tell you what is the expected behaviour in >> Darwin or BSD. If people usually use "unknown" in triples, this will >> break their

...ernal lld file format is an _intermediate_ data structure designed to make creating the final executable straightforward and fast. It isn't designed to be an executable format itself. In fact, the reason why linkers can often be slow is because the intermediate and final object file formats are conflated. davez On May 2, 2012, at 8:29 AM, Shea Levy <shea at shealevy.com> wrote: > Hello, > > Would it be feasible to use the internal lld file format as the native > executable format for an OS? Are there performance or space > considerations that would make this a poor choic...

On 29 Jan 2015, at 19:05, Greg Fitzgerald <garious at gmail.com> wrote: > > I'd think you'd see value when new languages get off the ground faster > because they don't need to think about linking. Dealing with all the > subtle differences between the various system linkers is no fun. > Maybe that's not a ton of value, but as I mentioned, the integration >

On 12/10/2010 11:37 PM, Ian Campbell wrote: > severity 606589 important > reassign 606589 xen-hypervisor-4.0-amd64 > merge 606590 606589 > thanks > > At the core this is the same issue as 606590. I think a single report is > enough to allow this to be fixed in the relevant place, if the kernel > ends up being the place to fix then the bug can be reassigned as >

On Thu, Jan 29, 2015 at 10:26 AM, Reid Kleckner <rnk at google.com> wrote: > It's not clear to me that this is worthwhile. I'd think you'd see value when new languages get off the ground faster because they don't need to think about linking. Dealing with all the subtle differences between the various system linkers is no fun. Maybe that's not a ton of value, but as I

On Jun 26, 2019, at 9:02 AM, Andrew Kelley via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 6/24/19 6:23 PM, Siva Chandra via llvm-dev wrote: >> Within Google, we have a growing range of needs that existing libc >> implementations don't quite address. >> To be very clear: we don't expect our needs to exactly match everyone >> else's -- part of our

...22, 2020 at 8:39 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: > > Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. > > > > I will continue to look into the issue with the methods Tomas mentioned. > > It is interesting that a rare 5 years old problem would re-appear on > current Insider builds. Which build of Windows are you running exactly? &g...

On 14 August 2014 11:13, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > Our Jenkins config just runs llvm-lit manually after building (we use Ninja not make in Jenkins because it's vastly faster for incremental builds and we have several LLVM forks / versions that we test). I agree that having a make / ninja target for the check would be useful, but the lit option was the