llvm dev - Jan 2009 - [LLVMdev] PATCH: llvm-top git support and out-of-tree building for llvm

What: The original scripts in llvm-top assume that they're dealing with 
a subversion working copy. The patch adds support for a git repository 
cloned using git svn.

The other two patches make llvm (core) do an out-of-tree build, i.e., 
the source tree is kept clean, and tells llvm-gcc-4.2 to find llvm in 
the right (new) place.

Why: Using git it is possible to fiddle locally with the code, have the 
original as well as the changes in version control, and keep up with 
updates from the central SVN repository.

Out-of-tree builds make it easier to distinguish what files are changed, 
added, or generated.

Michael

-- 
Michael Schuerig
mailto:michael at schuerig.de
http://www.schuerig.de/michael/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm-gcc-out-of-tree.diff
Type: text/x-diff
Size: 1212 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090119/ab2b868a/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm-out-of-tree.diff
Type: text/x-diff
Size: 1658 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090119/ab2b868a/attachment-0001.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm-top-git.diff
Type: text/x-diff
Size: 2714 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090119/ab2b868a/attachment-0002.diff>

Hi Michael,
> What: The original scripts in llvm-top assume that they're dealing with
> a subversion working copy. The patch adds support for a git repository 
> cloned using git svn.
> 
> The other two patches make llvm (core) do an out-of-tree build, i.e., 
> the source tree is kept clean, and tells llvm-gcc-4.2 to find llvm in 
> the right (new) place.
> 
> Why: Using git it is possible to fiddle locally with the code, have the 
> original as well as the changes in version control, and keep up with 
> updates from the central SVN repository.
> 
> Out-of-tree builds make it easier to distinguish what files are changed, 
> added, or generated.
these look good to me, but unfortunately I am unable to test them for
the moment, otherwise I would have applied them.

Ciao,

Duncan.

On Monday 19 January 2009, Duncan Sands wrote:
> these look good to me, but unfortunately I am unable to test them for
> the moment, otherwise I would have applied them.
Please don't skip the testing. I'm pretty new to LLVM and not a git 
expert either, so my changes may introduce subtle or not so subtle 
problems that I didn't think of.

Michael

-- 
Michael Schuerig
mailto:michael at schuerig.de
http://www.schuerig.de/michael/

Hi Michael, I've applied these (with some tweaks).
Thanks for working on this!

Ciao,

Duncan.

Hi,
I'm implementing storeRegToStackSlot() and, in order to store some specific
registers (floating point regs and address regs) I've to copy them to more
standard regs and copy these last ones to the slot.
I tried to generate instructions that use physical registers, but by doing that
I overwrote registers already assigned by the register allocator.
Is it possible to use virtual registers in the instructions generated by
storeRegToStackSlot()?
This function is called by the register allocator. So, if it needs to store regs
on a slot, this means that there is no more registers available. So, I cannot
believe that it is able to allocate new virtual registers generated by
storeRegToStackSlot().
What is the good way to implement this ?
Thanks a lot
Gab