search for: conflate

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). > >

...ves, instead of hand-wavy “I believe” discussions. > > > > Bear in mind that I gave you facts (bandwidth problems, turned off SVN > > services, constant breakdowns, expertise in handling traffic, backup > > solutions). > > And I consider many of the “facts” you gave to conflate other element than > hosting the repository *alone*, which makes it hard to me to see them as > relevant as-is. > > > > > I also made you aware that the human cost is not *just* Tanya and > > Anton, but also me and everyone else that maintains buildbots, > > externa...

...gt; I think (Hat: FreeBSD) we only expect to see unknown in the vendor field >>> (e.g. i386-unknown-freebsd). If the OS field is unknown, rather than >>> freebsd, then it's not one of ours and we aren't likely to care. I don't >>> really like the way that we conflate OS with ABI, but then I don't really >>> like anything about triples... >> >> David, thanks! >> >> >> Cheers, >> Jon >> >>> >>> David >>> >> >> -- >> Jon Roelofs >> jonathan at codesourcery.com...

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/Wri...

...eriment with, so no one tries out new performance techniques on it. There are two main issues here: 1) The R Language Definition doesn't get enough love. I could point out plenty of specific problems, omissions, etc., but I think the high-level problem is that the Language Definition currently conflates three things: 1) the actual language definition, 2) the definition of what is more properly the standard library, and 3) the implementation. This conflation hides how simple the R/S language actually is and, by assuming that the current implementation is the only implementation, obscures performan...

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...

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: >...

...interfacing with experimental hardare and so suffer the pain of C++ API changes on a fairly frequent basis. The C APIs generally feel clunky to use. If we have a stable C API that is useful, I'd love to see C++ wrappers so that we don't have to suffer things like iterators. Currently, we conflate 'C' and 'stable'. In many cases, I'd prefer a C++ API to a C one, or would be happy to write (or even use automatically generated) thin C wrappers around C++. The requirement is not the language, it's the stability. I presume this also applies to WebKit: there's no re...

...les are to mean the same thing? > > I think (Hat: FreeBSD) we only expect to see unknown in the vendor field (e.g. i386-unknown-freebsd). If the OS field is unknown, rather than freebsd, then it's not one of ours and we aren't likely to care. I don't really like the way that we conflate OS with ABI, but then I don't really like anything about triples... David, thanks! Cheers, Jon > > David > -- Jon Roelofs jonathan at codesourcery.com CodeSourcery / Mentor Embedded

...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 choi...

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? &...

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