Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Bazaar mirror?"
2010 Feb 02
0
[LLVMdev] About setting up official git & bzr mirrors.
Launchpad already maintains bzr mirrors:
http://code.launchpad.net/llvm
The mirrors are the lp:~vcs-import branches (a specific launchpad user used
for automatically mirroring branches).
Baptiste.
2009/10/28 Óscar Fuentes <ofv at wanadoo.es>
> Time ago when the svn server was crawling due to massive hammering from
> people mirroring the repo, someone said that after the 2.6 release
2009 Oct 28
6
[LLVMdev] About setting up official git & bzr mirrors.
Time ago when the svn server was crawling due to massive hammering from
people mirroring the repo, someone said that after the 2.6 release we
could discuss creating official mirrors for those who work with svn
clients based on distributed VCSs such as git and bazaar.
Such mirrors increase productivity (facilitating experimentation and
parallel tasks, allowing off-line work) and even lessens the
2008 Jul 27
0
[LLVMdev] Any Mercurial or Bazaar mirrors available?
I've been using git-svn successfully as a distributed front-end for
Subversion repositories. You get a complete, local Git repository from
where you can commit and update to/from Subversion. It works quite
well, actually.
Native Windows is entirely unsupported by Git at the moment, but I
hear it works well under Cygwin.
- Simon
2008/7/27 Óscar Fuentes <ofv at wanadoo.es>:
> Owen
2008 Jul 27
2
[LLVMdev] Any Mercurial or Bazaar mirrors available?
Owen Anderson <resistor at mac.com> writes:
> On Jul 26, 2008, at 7:56 PM, Óscar Fuentes wrote:
>> Having a private branch would be handy for some experiments I'm
>> doing. Two years ago there was an announcement by Owen Anderson, but
>> the repo seems down now.
>
> I haven't maintained that for a long time. I think there are some
> community members
2009 Oct 28
0
[LLVMdev] About setting up official git & bzr mirrors.
On Oct 28, 2009, at 8:30 AM, Óscar Fuentes wrote:
> Time ago when the svn server was crawling due to massive hammering
> from
> people mirroring the repo, someone said that after the 2.6 release we
> could discuss creating official mirrors for those who work with svn
> clients based on distributed VCSs such as git and bazaar.
>
> Such mirrors increase productivity
2010 Jan 28
2
[LLVMdev] About setting up official git & bzr mirrors.
Due to a current need to have a git mirror for LLVM, I'm resurrecting this old thread.
I'm aware that there exist already LLVM git mirrors at git://repo.or.cz/llvm.git and git://github.com/earl/llvm-mirror.git However, these repositories only mirror the current SVN trunk and do no provide any branch and tag information, which would be very convenient for creating experimental branches
2008 Jul 27
0
[LLVMdev] Any Mercurial or Bazaar mirrors available?
On Jul 26, 2008, at 7:56 PM, Óscar Fuentes wrote:
> Having a private branch would be handy for some experiments I'm
> doing. Two years ago there was an announcement by Owen Anderson, but
> the
> repo seems down now.
>
> --
> Oscar
>
I haven't maintained that for a long time. I think there are some
community members who use git mirrors, though.
--Owen
2008 Jul 27
2
[LLVMdev] Any Mercurial or Bazaar mirrors available?
Having a private branch would be handy for some experiments I'm
doing. Two years ago there was an announcement by Owen Anderson, but the
repo seems down now.
--
Oscar
2009 Jul 09
0
[LLVMdev] LLVM PPA with updated packages from svn + bazaar repos
Hey,
I started a PPA (basically an Ubuntu package repository) for LLVM,
I'm going to try to make packages with snapshots from llvm that are
updated at least weekly, so it's easier for people to try the latest
version from svn but not having to compile it and do everything themselves.
Hopefully this will be useful for people here, I still have some stuff to
do, and right now I've not
2009 Aug 26
4
[LLVMdev] Slow jitter.
Eli Friedman <eli.friedman at gmail.com> writes:
> On Tue, Aug 25, 2009 at 4:58 PM, Óscar Fuentes<ofv at wanadoo.es> wrote:
>> Eli Friedman <eli.friedman at gmail.com> writes:
>>
>>> On Wed, Aug 26, 2009 at 1:10 AM, Óscar Fuentes<ofv at wanadoo.es> wrote:
>>>> While compiling some sources, translating from my compiler's IR to LLVM
2011 Jan 14
2
[LLVMdev] Circular Deps from CMake build using makefile
----- Original Message ----
> From: Óscar Fuentes <ofv at wanadoo.es>
> To: Samuel Crow <samuraileumas at yahoo.com>
> Cc: Óscar Fuentes <ofv at wanadoo.es>; LLVM Developers Mailing List
><llvmdev at cs.uiuc.edu>
> Sent: Fri, January 14, 2011 4:39:57 PM
> Subject: Re: Circular Deps from CMake build using makefile
>
> Samuel Crow <samuraileumas
2013 Dec 18
0
[LLVMdev] [cfe-dev] LLVM 3.4 Branch Freeze
On Wed, Dec 18, 2013 at 10:57:58AM -0600, Hal Finkel wrote:
> ----- Original Message -----
> > From: "Tom Stellard" <tom at stellard.net>
> > To: "Hal Finkel" <hfinkel at anl.gov>
> > Cc: cfe-dev at cs.uiuc.edu, llvmdev at cs.uiuc.edu, "Óscar Fuentes" <ofv at wanadoo.es>
> > Sent: Wednesday, December 18, 2013 10:55:43 AM
2013 Dec 18
2
[LLVMdev] [cfe-dev] LLVM 3.4 Branch Freeze
----- Original Message -----
> From: "Tom Stellard" <tom at stellard.net>
> To: "Hal Finkel" <hfinkel at anl.gov>
> Cc: cfe-dev at cs.uiuc.edu, llvmdev at cs.uiuc.edu, "Óscar Fuentes" <ofv at wanadoo.es>
> Sent: Wednesday, December 18, 2013 10:55:43 AM
> Subject: Re: [cfe-dev] [LLVMdev] LLVM 3.4 Branch Freeze
>
> On Fri, Dec
2009 Aug 25
2
[LLVMdev] Slow jitter.
Eli Friedman <eli.friedman at gmail.com> writes:
> On Wed, Aug 26, 2009 at 1:10 AM, Óscar Fuentes<ofv at wanadoo.es> wrote:
>> While compiling some sources, translating from my compiler's IR to LLVM
>> using the C++ API requires 2.5 seconds. If the resulting LLVM module is
>> dumped as LLVM assembler, the file is 240,000 lines long. Generating
>> LLVM
2009 Aug 26
0
[LLVMdev] Slow jitter.
On Tue, Aug 25, 2009 at 4:58 PM, Óscar Fuentes<ofv at wanadoo.es> wrote:
> Eli Friedman <eli.friedman at gmail.com> writes:
>
>> On Wed, Aug 26, 2009 at 1:10 AM, Óscar Fuentes<ofv at wanadoo.es> wrote:
>>> While compiling some sources, translating from my compiler's IR to LLVM
>>> using the C++ API requires 2.5 seconds. If the resulting LLVM
2009 Aug 09
0
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
Eli Friedman <eli.friedman at gmail.com> writes:
> On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote:
>> I think most LLVM users on Windows are interested on X86 only. This
>> saves a lot of time on the build process and creates smaller
>> executables. Anyways, it they want all targets, it is simply a matter of
>> passing
2010 Dec 23
0
[LLVMdev] LLVM installation in Windows
Thanks a lot. It worked !!!
Akramul
--- On Wed, 22/12/10, Jim Grosbach <grosbach at apple.com> wrote:
From: Jim Grosbach <grosbach at apple.com>
Subject: Re: [LLVMdev] LLVM installation in Windows
To: "akramul azim" <bijoy123_8 at yahoo.com>
Cc: "Óscar Fuentes" <ofv at wanadoo.es>, "Anton Korobeynikov" <anton at korobeynikov.info>,
2011 Jan 31
2
[LLVMdev] Official git mirroring of llvm, clang, lldb, test-suite, etc.?
Óscar Fuentes <ofv at wanadoo.es> writes:
>> git-svn often doesn't work, especially if the other side also needs
>> git-svn.
>
> The git mirror would be read-only, so if you want to contribute changes
> to LLVM using git you need git-svn anyways.
I pull down changes from upstream much more frequently than I send
changes up. To send changes up, diff+patch+svn,
2009 Aug 09
2
[LLVMdev] modify cmakefiles to set the default triple of msvc and mingw to i686-pc-mingw
On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote:
>> Also, now msvc support multiple target. So it's better to set it as
>> ${LLVM_ALL_TARGETS}
>> It's can working, why not set it to:.
>
> I think most LLVM users on Windows are interested on X86 only. This
> saves a lot of time on the build process and creates smaller
>
2008 Mar 26
3
[LLVMdev] Wrong calling convention?
Take a look at llvm-gcc. Look for HandleAggregateShadowArgument.
Evan
On Mar 26, 2008, at 10:31 AM, Óscar Fuentes wrote:
> Óscar Fuentes <ofv at wanadoo.es> writes:
>
>> BTW, -fpcc-struct-return solves the case that motivated this thread.
>
> -fpcc-struct-return is an ABI change, hence it requires "compiling the
> world". Not acceptable.
>
> I'll