similar to: [LLVMdev] Re: keeping the style police happy with vim

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Re: keeping the style police happy with vim"

2005 Apr 10
1
Fwd: Re: [LLVMdev] new IA64 backend
Does anybody know if there is some tool to convert from WHIRL to LLVM? maybe some project under development? a similar project? Thanks > > --- Duraid Madina <duraid at octopus.com.au> wrote: > > Date: Fri, 18 Mar 2005 12:45:54 +0900 > > From: Duraid Madina <duraid at octopus.com.au> > > To: ahs3 at fc.hp.com, LLVM Developers Mailing List <llvmdev at
2005 Feb 14
0
LLVM February Status Update
Hi Everyone, Sorry for the long overdue status update, as you might guess, the holidays have been busy for everyone. :) Here's your periodic dose of updates on the progress of LLVM, which takes us from the LLVM 1.4 release until present CVS. I appologize if I forgot anything! Big Things: 1. Brian contributed a new SparcV8 backend, which (unlike the SparcV9 backend) uses the
2005 Mar 18
2
[LLVMdev] new IA64 backend
Andrew Lenharth wrote: > On Fri, 2005-03-18 at 05:04 +0900, Duraid Madina wrote: >> - No varargs > > What are your issues here? Or are they simply at the "not implemented > so I don't know" stage? The two bugs I mentioned (no varargs, no alloca) are pretty much two sides of the same coin: I'm ignoring the IA64 stack frame layout (for no good reason), so
2005 May 11
0
[LLVMdev] LLVM 1.5 Release Plan
Hello Duraid, Duraid Madina wrote on Wednesday, 11 May 2005: >> I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I >> have installed to /opt/gcc > ... then you should either add /opt/gcc/lib to /etc/ld.so.conf and > rerun ldconfig, or add /opt/gcc/lib to your LD_LIBRARY_PATH . > However, GCC 4.x definitely has issues building LLVM, at least on > ia64. Oh,
2005 Mar 17
0
[LLVMdev] new IA64 backend
On Fri, 2005-03-18 at 05:04 +0900, Duraid Madina wrote: > Hi everyone, > > I've just checked in an IA64 backend to LLVM! Be warned, it's pretty > rough right now. Here are some of the known defects: > > - No varargs What are your issues here? Or are they simply at the "not implemented so I don't know" stage? Namely, I am working on some varargs
2005 Mar 17
0
[LLVMdev] new IA64 backend
On Fri, 2005-03-18 at 05:04 +0900, Duraid Madina wrote: > I've just checked in an IA64 backend to LLVM! Woo hoo! And There Was Much Rejoicing in IA64 Land :-). -- Ciao, al ---------------------------------------------------------------------- Al Stone Alter Ego: Linux & Open Source Lab Debian Developer Hewlett-Packard
2005 Mar 18
0
[LLVMdev] new IA64 backend
On Fri, 18 Mar 2005, Duraid Madina wrote: >>> - No instruction scheduling/bundling of any sort >> >> So this one needs to be coordinated. Next week, I might see about >> adding MachineInstruction support to the SelectionDAG so you can load up >> a DAG post-ISel and then spit it back out scheduled. > > That would be much appreciated, particularly if it
2002 Oct 07
1
[LLVMdev] VIM syntax highlighting
I have made a vim syntax highlighting script for LLVM. It can be found at llvm/utils/vim/llvm.vim. You should copy this file to your ~/.vim/syntax/ directory and add the following lines to your .vimrc file to have it automatically load on a .ll file. augroup filetype au! BufRead,BufNewFile *.ll set filetype=llvm augroup END Misha claims to be making a script for all you emacs
2010 Oct 30
0
[LLVMdev] Vim auto completion
The clang patches are now applied, so vim auto completion now works mostly out-of-the-box -- just build clang, set up your PATH for clang and clang++, and copy utils/vim/vimrc to ~/.vimrc (or symlink, or do your own thing). To configure the clang command-line, look for the g: configuration variables in the vimrc file. I'm open to suggestions about the handling of function parameters. One
2013 Feb 28
0
[LLVMdev] Propose to use rest.vim for vimrc of LLVM
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
2004 Dec 30
0
[LLVMdev] Primer with LLVM
On Thu, 2004-12-30 at 11:14, Francisco Puentes wrote: > Hi, everybody: > Hi Francisco > > I am a beginner with LLVM, in fact today was the first day that I use it. Welcome! > > I have several questions about LLVM: If you haven't already, a good place to start is the Getting Started Guide, at http://llvm.cs.uiuc.edu/docs/GettingStarted.html > Can I use LLVM to
2013 Feb 28
2
[LLVMdev] Propose to use rest.vim for vimrc of LLVM
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
2005 Jan 10
4
[LLVMdev] Version Control Upgrade?
I have used Perforce also and fully agree it's wonderful. The only concern I have is with their license for open source projects. The only gotcha is that it must be renewed annually, and they reserve the right to not renew it (though they say they won't unreasonably deny renewals). Not sure how much this really matters, as Perforce strikes me as being one of those "do no
2005 May 25
3
[LLVMdev] llc -march=ia64 support
You are right, the machine I am on is a AMD Opteron. I could probably generate working code for x86, but I am testing the implications of using 64 bits integers. The four weeks is not really important, it's just that it would be nice to have really fast code to showcase. Something related to this: to test the effect of 64 bits integers I replace all reference of int by long in my .ll file.
2010 Oct 21
0
[LLVMdev] Vim auto completion
On Oct 21, 2010, at 2:11 PM, Tobias Grosser wrote: > Hi, > > I have been watching the vim/clang autocompletion in utils/vim/vimrc for a while. What is the status of this work? The last information I got is, that there where still some patches missing, but this was before the clang-2.8. > Any updates? Is it supposed to work with clang-2.8? It requires a clang patch, which I
2016 Oct 29
1
Stupid vim question
On 10/29/2016 04:32 PM, Alice Wonder wrote: > On 10/29/2016 03:06 PM, Alice Wonder wrote: >> On 10/29/2016 02:49 PM, Frank Cox wrote: >>> On Sat, 29 Oct 2016 14:39:03 -0700 >>> Alice Wonder wrote: >>> >>>> How do I get it to stop doing that? >>> >>>
2007 Jun 28
3
Vim differences between C4 and C5
I have installed CentOS 4.5 and 5 on 2 separate machines, and both have default installs of vim-enhanced on each of them. I noticed that I can get syntax highlighting as a regular user, sudo and as root in C4.5. In C5 I only get highlighting as a regular user. I diff'ed my /etc/vimrc files between each install there is no changes and neither root ~ has a .vimrc file. I had put "# vim:
2005 Mar 18
1
[LLVMdev] new IA64 backend
On Thu, 2005-03-17 at 23:31 -0600, Chris Lattner wrote: > On Fri, 18 Mar 2005, Duraid Madina wrote: > >>> - No instruction scheduling/bundling of any sort > >> > >> So this one needs to be coordinated. Next week, I might see about > >> adding MachineInstruction support to the SelectionDAG so you can load up > >> a DAG post-ISel and then spit it
2005 Jun 01
0
[LLVMdev] 64-bit Linux Support
On Wed, Jun 01, 2005 at 10:50:35AM -0400, Bill Wendling wrote: > It didn't look like there was a cftonend binary for the IA-64 > platform. Are we supposed to use the x86 binaries instead? The answer to that is that we don't have IA-64 in-house, so we don't provide an IA-64 C/C++ front-end, but if someone were to contribute it to us, we would gratefully host it. Note that if you
2016 Oct 29
0
Stupid vim question
On 10/29/2016 03:06 PM, Alice Wonder wrote: > On 10/29/2016 02:49 PM, Frank Cox wrote: >> On Sat, 29 Oct 2016 14:39:03 -0700 >> Alice Wonder wrote: >> >>> How do I get it to stop doing that? >> >> http://superuser.com/questions/278442/how-to-make-vim-not-fold-everything-automatically >> >> > > Thank you, it appears the folding is the term