search for: dslextrem

Chris Lattner wrote: > Patches welcome. Please send a patch, or even just some suggested > text, and we'll be happy to include it. Remember that the people who > usually end up writing the FAQ's already know all the answers, so it's > hard for us to see things from fresh perspectives sometimes :) > > -Chris > Actually, my request for more info in the

On 01/02/2010 11:24 AM, Bob Wilson wrote: > Yes, that is correct. It is supported in the trunk sources, but it has > not yet been released. Hmm. Would the same also be true of the "inbounds" keyword for GEP? It doesn't seem to be recognized ("expected type"). Dustin

On Sat, Jan 2, 2010 at 2:31 PM, Dustin Laurence <dllaurence at dslextreme.com> wrote: > On 01/02/2010 11:24 AM, Bob Wilson wrote: > >> Yes, that is correct.  It is supported in the trunk sources, but it has >> not yet been released. > > Hmm.  Would the same also be true of the "inbounds" keyword for GEP?  It > doesn't seem to...

...ssor macro you can get in LLVM Assembly since it doesn't have a preprocessor at all. LLVM does aggressive inlining for functions used only once so those instances don't require specification as alwaysinline. --Sam ----- Original Message ---- > From: Dustin Laurence <dllaurence at dslextreme.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sat, January 9, 2010 3:46:29 AM > Subject: Re: [LLVMdev] Inlining > > > Also, drop the alwaysinline attribute and '-always-inline' flag. The > > normal inliner (aka. "opt -inline" which is run as part of "...

On Sat, Jan 9, 2010 at 12:57 PM, Dustin Laurence <dllaurence at dslextreme.com> wrote: > I have yet another question that I believe also stems from deep > ignorance of the linkage types.  How do you declare a global variable > without defining it?  The IR ref. clearly indicates that you can do > this, but it looks like one of the many "too obvious to...

Here is a patch that cleans up a couple of bugs and makes what I think are a couple of small improvements based on the recent advice about structs that I got. There is more like this that could be done, but I wanted to see how this example was received. Dustin -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: LangRef.struct.patch URL:

Awesome, thanks! Committed as r93170 with the following change: s/local variables/registers/. "Local variable" refers to allocas in LLVM, rather than %whatever SSA "variables". On Mon, Jan 11, 2010 at 1:28 AM, Dustin Laurence <dllaurence at dslextreme.com> wrote: > Here is a patch that cleans up a couple of bugs and makes what I think > are a couple of small improvements based on the recent advice about > structs that I got.  There is more like this that could be done, but I > wanted to see how this example was received.

hi, I am running CENTOS 4.3 on my IBM thinkpad T30, (recently switch from Fedora 5), and would like to have the icon of my battery remaining and my cpuspeed control. but could not find anywhere only the klaptop_check wich i do not like too much, i am using acpi, could anyone please tell which aplication do i need to install or how do i execute it? thanks a lot, regards, Guillermo Garron

lcs for language compiling system? It's a suggestive of the old name, easy to remember, easy to say, and seems to be easy to google. Advanced could be prepended to it to make it alcs to make it even more unique. -e

Erick Tryzelaar wrote: > Actually, my request for more info in the "Getting Started" had some > hidden questions, as I don't know the answer to them :) So to be a > little more clear, here are the two I had: > > Does the gcc4 no longer need the "fixheaders" script that the gcc3.4 > frontends uses? > > Is it possible to install both the gcc4 and

On 01/11/2010 11:20 AM, Jeffrey Yasskin wrote: > Awesome, thanks! Committed as r93170 with the following change: > > s/local variables/registers/. "Local variable" refers to allocas in > LLVM, rather than %whatever SSA "variables". Excellent. I was not actually happy with that term when I wrote it, but wasn't sure of the standard terminology. It should

...ides such a portable interface to libc for LLVM? If not, I'll write my own routines, but if there is a way to adopt a common standard or avoid reinventing the wheel I'm all for it. Mike -------------------------------------------------- From: "Dustin Laurence" <dllaurence at dslextreme.com> Sent: Friday, February 12, 2010 12:10 PM To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] Portable I/O > On 02/12/2010 09:51 AM, Chris Lattner wrote: > >> I think that the point is that you can define your own standard runtime...

On 01/08/2010 09:17 PM, Nick Lewycky wrote: > Try using 'internal' linkage instead of 'linkonce'. That did it, thanks. --- gemini:~/Projects/LLVM/Tests/Inline(0)$ cat testInline.optdis.ll ; ModuleID = 'testInline.optbc' define i32 @main(i32 %argc, i8** nocapture %argv) nounwind readnone { ret i32 42 } gemini:~/Projects/LLVM/Tests/Inline(0)$ --- > If you're

On 02/12/2010 09:51 AM, Chris Lattner wrote: > I think that the point is that you can define your own standard runtime interfaces: > > void *myopen(const char*path) { > return fopen(path, ...); > } Maybe my experience hand-coding LLVM will actually be of some help. What I did for this case is what I think Chris is suggesting--I have a .c file with functions that return

...as far behind schedule as it is. I'd better do some experimenting sometime with opaque types and inlines together to see if they work as expected for producing easy macros. Anyway, sorry for drifting off-topic, --Sam ----- Original Message ---- > From: Dustin Laurence <dllaurence at dslextreme.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sat, January 9, 2010 12:35:33 PM > Subject: Re: [LLVMdev] Inlining > > On 01/09/2010 10:00 AM, Samuel Crow wrote: > > > > Always inline is the closest to a preprocessor macro you can get in > > LLVM Assembly since it d...

On 01/09/2010 10:00 AM, Samuel Crow wrote: > > Always inline is the closest to a preprocessor macro you can get in > LLVM Assembly since it doesn't have a preprocessor at all. Mine does. :-) > ...LLVM does > aggressive inlining for functions used only once so those instances > don't require specification as alwaysinline. What I'm trying to do is understand the

I have yet another question that I believe also stems from deep ignorance of the linkage types. How do you declare a global variable without defining it? The IR ref. clearly indicates that you can do this, but it looks like one of the many "too obvious to mention" things that I struggle with. It's easy with functions, of course: "declare @foo" in the header and

Hi Everyone, LLVM is a growing project, and many of us are very fond of it. :) LLVM is continuing to grow, both in maturity in specific areas and in scope of areas that it is applicable to. When we first started the project, we focused on the design of the intermediate representation. It is a strong design goal that the IR be a self-contained virtual instruction set, which fully describes

Hello, I have a question about the indirectbr instruction. I attempted to use it according to the example in the Assembly Language Reference manual, but got an "expected instruction opcode" error. Poking about on the web I found this document: http://nondot.org/sabre/LLVMNotes/IndirectGoto.txt which appears to be a Nov 2, 2009 proposal to add indirectbr and blockaddress() to the IR

Hello, I have a question about the indirectbr instruction. I attempted to use it according to the example in the Assembly Language Reference manual, but got an "expected instruction opcode" error. Poking about on the web I found this document: http://nondot.org/sabre/LLVMNotes/IndirectGoto.txt which appears to be a Nov 2, 2009 proposal to add indirectbr and blockaddress() to the IR