similar to: [LLVMdev] Does getelementptr get optimized in compile-time?

Hello Duncan Sands, > If however the operands are all numerical values (eg the pointer operand is "null" and the others are numbers like "1") then it will be turned into a number by the optimizers. I think my case is stated above among your answer. http://nondot.org/sabre/LLVMNotes/SizeOf-OffsetOf-VariableSizedStructs.txt There is a brief document about using

Hi Journeyer, > I've got a question about getelementptr. > > I've been told that getelementptr is evaluated in compile-time NOT in run-time. this is impossible if the arguments are not constants. If they are constant, then the optimizers will turn a getelementptr instruction into a getelementptr constant expression (http://llvm.org/docs/LangRef.html#constant-expressions). Even

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

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 Journeyer 2013/1/15 Justin Holewinski <justin.holewinski at gmail.com>: > Is this for user prompts, or just reading data from stdin? You can use >

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

On Fri, May 2, 2008 at 1:22 PM, Marc de Kruijf <dekruijf at cs.wisc.edu> wrote: > The LLVA and LLVM papers motivate the GetElementPtr instruction by arguing > that it abstracts implementation details, in particular pointer size, from > the compiler. While it does this fine for pointer addresses, it does not > manage it for address offsets. Consider the following code: > >

> 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

The LLVA and LLVM papers motivate the GetElementPtr instruction by arguing that it abstracts implementation details, in particular pointer size, from the compiler. While it does this fine for pointer addresses, it does not manage it for address offsets. Consider the following code: $ cat test.c int main() { int *x[2]; int **y = &x[1]; return (y - x); } $ llvm-gcc -O3 -c test.c

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 branches and each branch is for

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

Hi Sean Silva, Maybe I am the only one who is trying to use UML. In my team, I am also the only one who draws UML diagrams. I expected 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

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

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

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

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

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

Hello Peng Yu, I found the same error on my Macbook Air. This was my first trying on MacOS X. Troubleshooting this might take sometime. Only thing I can say now that klang is tested successfully on Ubuntu with - LLVM 3.2 official release on LLVM download page - LLVM svn latest update Clang compile produces an error message on MacOS X with the LLVM svn latest update I am trying to find the

Is this for user prompts, or just reading data from 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: >

> I divided toy.cpp into several .cpp and .h files in several directories. > The purpose of this work is making it structured similar to clang. > And I put it up to github. > > git://github.com/Journeyer/klang.git This is a brilliant idea. This is the perfect way to get familiar with LLVM (and Clang, to some extent). > Now I wonder what license should this work follow or if it

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