search for: inseparably

...so, presumably LLD is going to be giving sweet diagnostics some day, > and this change would be analogous to the work that Michael Spencer > has been doing lifting and generalizing the option-parsing stuff from > Clang. What do you think about that approach? clang's diagnostic code is inseparably tied to clang's SourceManager, which really only makes sense for code using clang's Lex library. It might make sense to have a simpler diagnostic printing library in LLVM even if clang can't use it. -Eli

On Fri, 2008-04-04 at 12:15 -0700, Evan Cheng wrote: > On Apr 4, 2008, at 11:58 AM, Jonathan S. Shapiro wrote: > > > In general, it is not possible to know jitted code size without > > emitting. You can suppress the actual write of the instructions > > themselves, but you have to do all of the work prior to that point. > > That's not true. llvm targets which

> IMO, the right way to build this is something like > "InlineAsmDiagnosticHandler" in LLVMContext (but hopefully better, and more > structured :) Hey Chris, Did you catch my suggestion in reply to Hal, about maybe generalizing Clang's diagnostics infrastructure up into LLVM? Your reply seems along the same lines. It seems like a natural fit to reuse that rather than make

Hello. I have a problem regarding the output from the R plot window. I have a quite dense dendrogram that I wish to visualize using a suitable software (like Illustrator), and to accomplish that I right click on the image from the plotting device and I save as metafile. The problem is when I scale up the image, some of the vectors in the dendrogram image are inseparable. My question is if

On Fri, 4 Apr 2008, Jonathan S. Shapiro wrote: > Evan: please explain how span-dependent branches are resolved in your > method. You don't need to compute the bits that will be emitted, but you > do need to compute the length of those bits. In most real > implementations, the two steps are therefore inseparable. I think the important point here is that llvm explicitly represent

I built a new server about 10 days ago running CentOS 5.latest, and it's been presenting a message shortly after booting: irq 58: nobody cared (try booting with the "irqpoll" option) Call Trace: <IRQ> [<ffffffff800bb712>] __report_bad_irq+0x30/0x7d [<ffffffff800bb945>] note_interrupt+0x1e6/0x227 [<ffffffff800bae41>] __do_IRQ+0xbd/0x103

We use a home-brew system similar to fail2ban to block traffic from IP addresses which appear to be doing Nasty Things(tm). The main thing our system does that fail2ban doesn't is to use a central DNSRBL we maintain allowing it to immedatiately ban listed IP addresses the first time they make an attempt to connection without waiting for them to hit a sufficient number of times to bring up the

Hello, I would like to compile the Ogg Vorbis libraries and tools on my Slackware 7.0 box. Unfortunatelly Slack is comming with gcc 2.91.66 which is not suited for compilation of these libraries and tools. I downloaded, compiled and installed in a separate directory tree gcc 2.95.3 but now I really don't know how to make the configure script see it and set it properly as the compiler to be

On Apr 4, 2008, at 11:58 AM, Jonathan S. Shapiro wrote: > In general, it is not possible to know jitted code size without > emitting. You can suppress the actual write of the instructions > themselves, but you have to do all of the work prior to that point. That's not true. llvm targets which support JIT have all the information necessary to calculate the size of every

https://bugzilla.samba.org/show_bug.cgi?id=3829 Summary: rsync loses access ACLs on transferred files Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: hashproduct+rsync@gmail.com

In general, it is not possible to know jitted code size without emitting. You can suppress the actual write of the instructions themselves, but you have to do all of the work prior to that point. The reason is that on many architectures there are span-dependent branches. The final instruction size depends on the branch span. The span depends on the code size, and the code size depends on the

My Centos 5.2 box shuts itself down during a long tar -x. There is plenty of disk available. This is new; it worked in the past. Any suggestions? Thanks, Mike.

Greetings all, This isn't a request for help, but I thought the following article from the New York Times would be of interest to you all. Enjoy! Adam *Data Analysts Captivated by R's Power* By ASHLEE VANCE Published ONLINE: January 6, 2009 URL: http://www.nytimes.com/2009/01/07/technology/business-computing/07program.html A version of this article appeared in print edition on

This article is accompanied by nice pictures of Robert and Ross. Data Analysts Captivated by Power of R http://www.nytimes.com/2009/01/07/technology/business-computing/07program.html January 7, 2009 Data Analysts Captivated by R?s Power By ASHLEE VANCE To some people R is just the 18th letter of the alphabet. To others, it?s the rating on racy movies, a measure of an attic?s insulation or

From: Les Mikesell <lesmikesell at gmail.com> > Can you get the product without being bound by the restrictions? > That is, can one user purchase one and resell copies without the SLA > or with their own? Not with the trademark, that is mis-appropriation. If you want to complain about Red Hat doing this, then you'll want to complain about a number of distributors well before

I have RSI (hurty hands) and need software for recognition of continuous speech. Linux has nothing workable. Dragon was bad even on Windows. What's needed is a Linux speech engine, so that the linux crew can get making a good GUI. So I'm trying to bring over the Vista Speech Engine. Here's my (failed) attempt: http://womblezone.blogspot.com/ I'm trying to bring it over with

Hello LLVM Developers, Within Google, we have a growing range of needs that existing libc implementations don't quite address. This is pushing us to start working on a new libc implementation. Informal conversations with others within the LLVM community has told us that a libc in LLVM is actually a broader need, and we are increasingly consolidating our toolchains around LLVM. Hence, we