search for: oosaprogramm

On Sat, Dec 29, 2012 at 9:45 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Klang is tested with LLVM 3.1 > Header file location is often changed. I guess that's why.. I think that klang should be based on the latest SVN/git version of LLVM. -- Sean Silva

...d about this also. This will be done as soon as possible. (Before I fix this, If you look at the commits for this issue for master branch, you can easily fix it and test for others also.) Sorry for the late update. Thank you for the concern. Best regards Journeyer 2012/12/30 Journeyer J. Joh <oosaprogrammer at gmail.com>: >> I think that klang should be based on the latest SVN/git version of LLVM. > > OK. I am testing it with LLVM 3.2 wait a minute. > -- Journeyer > > 2012/12/30 Sean Silva <silvas at purdue.edu>: >> On Sat, Dec 29, 2012 at 9:45 PM, Journeyer J. Jo...

On Sat, Dec 29, 2012 at 7:30 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hello Peng Yu and List, > > I have put toy.cpp into github but it has a form of LLVM project > makefile infrastructure. So you can build it together with LLVM > Project source tree. > > git://github.com/Journeyer/klang.git > > There exist many...

...moryBuffer::getSTDIN to read the contents of stdin into a memory buffer. > Then you can get the data pointer and size and read it in. As far as I > know, there is not a good way to implement user prompts with the LLVM APIs. > > > On Mon, Jan 14, 2013 at 4:57 AM, Journeyer J. Joh <oosaprogrammer at gmail.com> > wrote: >> >> Hello list, >> >> I learned that under LLVM, #including of <iostream> is forbidden. >> Instead LLVM provides llvm::raw_ostream(for std::cout, std::cerr) and >> llvm::MemoryBuffer(for input stream). >> >> And...

And for this kind of question I think I would better hold in. There would be more important issue worth on this list. For this reason I am sorry. Sincerely Journeyer 2013/1/15 Journeyer J. Joh <oosaprogrammer at gmail.com>: > Hi Justin Holewinski, > >>> As far as I know, there is not a good way to implement user prompts with the LLVM APIs. > > This info helps me a lot. > I tried to do a thing that is not possible. > > Thank you very much. > > Sincerely > Journ...

Klang is tested with LLVM 3.1 Header file location is often changed. I guess that's why.. What version of LLVM do you use? 2012/12/30 Peng Yu <pengyu.ut at gmail.com>: > On Sat, Dec 29, 2012 at 7:30 PM, Journeyer J. Joh > <oosaprogrammer at gmail.com> wrote: >> Hello Peng Yu and List, >> >> I have put toy.cpp into github but it has a form of LLVM project >> makefile infrastructure. So you can build it together with LLVM >> Project source tree. >> >> git://github.com/Journeyer/klang.git...

> I think that klang should be based on the latest SVN/git version of LLVM. OK. I am testing it with LLVM 3.2 wait a minute. -- Journeyer 2012/12/30 Sean Silva <silvas at purdue.edu>: > On Sat, Dec 29, 2012 at 9:45 PM, Journeyer J. Joh > <oosaprogrammer at gmail.com> wrote: >> Klang is tested with LLVM 3.1 >> Header file location is often changed. I guess that's why.. > > I think that klang should be based on the latest SVN/git version of LLVM. > > -- Sean Silva -- ---------------------------------------- Journ...

...cted there be someone who use UML like me. But it's maybe not as your opinion. Maybe doxygen is enough for majority of people. Thanks for your reply. Sincerely Journeyer J. Joh 2012/12/25 Sean Silva <silvas at purdue.edu>: > On Mon, Dec 24, 2012 at 2:08 AM, Journeyer J. Joh > <oosaprogrammer at gmail.com> wrote: >> Do you use one of these tools? If so let me know your experience. >> And I don't believe people use these to generate code for LLVM/Clang. > > I personally don't use any tool like that. > > My impression is that most developers here do no...

On Tue, Oct 2, 2012 at 11:44 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hi list, > > I have a simple question about LLVM. > > I learned that we need to use iterations than recursions in C programming. > That is because recursion is expensive. It can easily consume out all > the stack given to a program. And the call/retu...

Hello list, I'd like to know if people use UML tool to analyze and/or document LLVM/Clang. I use StarUML. It's free and very good though it's free. But I consider using a commercial program. Because the organization I belong is willing to support for this. I don't think I will use these tools to write code. I think I will use these to do a documentation and analyze code. So the

On Mon, Dec 24, 2012 at 2:08 AM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Do you use one of these tools? If so let me know your experience. > And I don't believe people use these to generate code for LLVM/Clang. I personally don't use any tool like that. My impression is that most developers here do not use any kind of UML code...

Hello Peng Yu and List, I have put toy.cpp into github but it has a form of LLVM project makefile infrastructure. So you can build it together with LLVM Project source tree. git://github.com/Journeyer/klang.git There exist many branches and each branch is for each chapter of Kaleidoscope. Regards Journeyer 2012/12/30 Peng Yu <pengyu.ut at gmail.com>: > Hi, > > I'm learning

Oh I see. Thank you. I will study that. Journeyer 2013/1/13 Sean Silva <silvas at purdue.edu>: > You can easily collect this information with DTrace on a Mac (or > Solaris or FreeBSD) without any special LLVM instrumentation. > > -- Sean Silva -- ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m

On Sat, Jan 12, 2013 at 10:00 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Oh I see. Thank you. I will study that. You will want to use the pid provider. The most basic thing you can probably do is to turn on flowindent and just trace `pid$target:::entry' and `pid$target:::return`, which will trace all the function calls and returns. Th...

Thanks, Journeyer. I applied the patch with r176235. In future, you can submit patches to the llvm-commits mailing list. :) -bw On Feb 27, 2013, at 9:03 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Hello list, > > I use LLVM's vimrc and found that this setting below is useful when > editing of reStructuredText file. > > > llvm/utils/vim/vimrc > > " Enable syntax highlighting for reStructuredText files. To use, copy > &quo...

Hi list, I have a simple question about LLVM. I learned that we need to use iterations than recursions in C programming. That is because recursion is expensive. It can easily consume out all the stack given to a program. And the call/return consumes time much more. But I've read a sentence that nowadays compilers can optimize recursions in C or whatever languages not to consume heavy stack

...te Clang compile produces an error message on MacOS X with the LLVM svn latest update I am trying to find the problem. And might need a help. Best regards Happy New Year! Journeyer 2013/1/1 Peng Yu <pengyu.ut at gmail.com>: > On Sun, Dec 30, 2012 at 12:19 AM, Journeyer J. Joh > <oosaprogrammer at gmail.com> wrote: >> Hello, >> >> I just applied changes of LLVM 3.2 and it is tested with LLVM 3.2 >> downloaded from the LLVM Download Page. >> >> I just worked for master branch only. >> The rest of the other branches need to be changed about thi...

Hi, I'm learning the tutorial. http://llvm.org/docs/tutorial/ I'm wondering if there is already a git repository of the examples in the tutorial so that I don't have to copy the code from the webpage. Thanks! -- Regards, Peng

...stdin? You can use MemoryBuffer::getSTDIN to read the contents of stdin into a memory buffer. Then you can get the data pointer and size and read it in. As far as I know, there is not a good way to implement user prompts with the LLVM APIs. On Mon, Jan 14, 2013 at 4:57 AM, Journeyer J. Joh <oosaprogrammer at gmail.com>wrote: > Hello list, > > I learned that under LLVM, #including of <iostream> is forbidden. > Instead LLVM provides llvm::raw_ostream(for std::cout, std::cerr) and > llvm::MemoryBuffer(for input stream). > > And using of llvm::raw_ostream is pretty easy...

Hello list, I use LLVM's vimrc and found that this setting below is useful when editing of reStructuredText file. llvm/utils/vim/vimrc " Enable syntax highlighting for reStructuredText files. To use, copy " rest.vim (http://www.vim.org/scripts/script.php?script_id=973) " to ~/.vim/syntax . augroup filetype au! BufRead,BufNewFile *.rst set filetype=rest augroup END