Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] Possible SVN breakage"
2009 Jul 27
3
[LLVMdev] [Cygwin] error building llvm-gcc - X86ATTAsmPrinter error in libstdc++
I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3 right
near the end of compiling llvm-gcc in valarray-inst.cc.
assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow scaling
by ESP"
Does this build on Linux ?
My remote Linux box has died and not a ble to reset it for a day or two.
/home/ang/build/llvm-gcc/./gcc/xgcc -shared-libgcc
2009 Feb 27
1
[LLVMdev] -fPIC warning on every compile on Cygwin
On Fri, Feb 27, 2009 at 7:14 AM, Nick Lewycky <nicholas at mxc.ca> wrote:
> Aaron Gray wrote:
> > On Sat, Feb 21, 2009 at 7:14 PM, Nick Lewycky <nicholas at mxc.ca
> > <mailto:nicholas at mxc.ca>> wrote:
> >
> > Aaron Gray wrote:
> > > On Thu, Feb 19, 2009 at 6:55 PM, Nick Lewycky <nicholas at mxc.ca
> >
2009 Feb 27
4
[LLVMdev] -fPIC warning on every compile on Cygwin
On Fri, Feb 27, 2009 at 4:32 PM, Jay Foad <jay.foad at gmail.com> wrote:
> >> Could you please rig Makefile.rules or something to print out the value
> >> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if
> >> that's erroneously false.
>
> This works for me:
>
> Index: Makefile.rules
>
2009 Jul 27
0
[LLVMdev] [Cygwin] error building llvm-gcc - X86ATTAsmPrinter error in libstdc++
This looks like pr4572.
Evan
On Jul 27, 2009, at 3:25 AM, Aaron Gray wrote:
> I am now getting an X86ATTAsmPrinter error in compiling libstdc++-v3
> right near the end of compiling llvm-gcc in valarray-inst.cc.
>
> assertion "IndexReg.getReg() != X86::ESP && "X86 doesn't allow
> scaling by ESP"
>
> Does this build on Linux ?
>
> My
2010 Aug 03
2
[LLVMdev] CMake error on Win32
I am getting the following error from CMake :-
CMake Error at CMakeLists.txt:227 (set_property):
set_property given invalid scope CACHE. Valid scopes are GLOBAL,
DIRECTORY, TARGET, SOURCE, TEST.
Can someone familiar with CMake deal with this please,
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Feb 27
0
[LLVMdev] -fPIC warning on every compile on Cygwin
On Fri, Feb 27, 2009 at 4:50 PM, Aaron Gray <aaronngray.lists at googlemail.com
> wrote:
> On Fri, Feb 27, 2009 at 4:32 PM, Jay Foad <jay.foad at gmail.com> wrote:
>
>> >> Could you please rig Makefile.rules or something to print out the value
>> >> of $(LLVM_ON_WIN32) ? The only way I can think of this happening is if
>> >> that's
2009 Jul 26
2
[LLVMdev] [Cygwin] error building llvm-gcc
Hi Daniel,
2009/7/26 Daniel Dunbar <daniel at zuster.org>
> Hi Aaron,
>
> Which revision are you building?
77074
>Assuming TOT, it's possible this is a bug that I introduced/triggered
>with the name changes.
Yes I am now getting the following :-
c++ -c -g -DIN_GCC -W -Wall -Wwrite-strings -pedantic -Wno-long-long
-Wno-variad
ic-macros -Wmissing-format-attribute
2009 Jul 02
4
[LLVMdev] OCAML and ocamldoc requirements on building andinstalling LLVM
> On Thu, Jul 2, 2009 at 11:46 AM, Aaron
> Gray<aaronngray.lists at googlemail.com> wrote:
>> Jon,
>>
>> LLVM seems to be now dependant by default on OCAML and ocamldoc. Can you
>> please change this so OCAML is only built and enabled when an
>> '--enable-ocaml' flag is set on 'configure'. As I cannot do 'make
>> install'
2009 Feb 23
2
[LLVMdev] make-test dependencies on local directory
On Feb 23, 2009, at 10:30 AMPST, Aaron Gray wrote:
> On Mon, Feb 23, 2009 at 6:22 PM, Aaron Gray <aaronngray.lists at googlemail.com
> > wrote:
> On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com>
> wrote:
> These benchmarks are not distributed with llvm (which doesn't have the
> legal right to distribute Spec, for example). If you have
2010 Aug 03
0
[LLVMdev] CMake error on Win32
Aaron Gray <aaronngray.lists at gmail.com> writes:
> I am getting the following error from CMake :-
>
> CMake Error at CMakeLists.txt:227 (set_property):
>
> set_property given invalid scope CACHE. Valid scopes are GLOBAL,
>
> DIRECTORY, TARGET, SOURCE, TEST.
>
>
> Can someone familiar with CMake deal with this please,
Please upgrade to cmake
2009 Jul 18
3
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
2009/7/18 Chris Lattner <clattner at apple.com>
>
> On Jul 18, 2009, at 2:56 PM, Aaron Gray wrote:
>
> I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
>
>
> If you're iterating over functions, just ignore all intrinsics.
>
Okay, but it would be nice if the Module object reflected the lowered symbol
names like 'memcpy' too.
2009 Jul 16
2
[LLVMdev] [patch] CodeEmitter Memory Foot Reduction
On Thu, Jul 16, 2009 at 10:04 AM, Aaron
Gray<aaronngray.lists at googlemail.com> wrote:
> 2009/7/16 Chris Lattner <clattner at apple.com>
>> Whats Daniels approach, does he have any online documentation or code, do
>> you have an email address so I may talk to him.
>>
>> Take a look at how asmprinters work
>> in include/llvm/Target/TargetRegistry.h .
2015 Sep 29
2
Fwd: buildbot failure in LLVM on clang-ppc64-elf-linux2
This buildbot appears to have been failing for several weeks now (
http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux2/builds/19490 ).
Does anyone know/own/care about it?
---------- Forwarded message ----------
From: <llvm.buildmaster at lab.llvm.org>
Date: Mon, Sep 28, 2015 at 11:17 PM
Subject: buildbot failure in LLVM on clang-ppc64-elf-linux2
To: Aaron Ballman <aaron at
2009 Jul 26
0
[LLVMdev] [Cygwin] error building llvm-gcc
On Sun, Jul 26, 2009 at 11:41 AM, Aaron
Gray<aaronngray.lists at googlemail.com> wrote:
> 2009/7/26 Daniel Dunbar <daniel at zuster.org>
> lvm-backend.o
> /home/ang/svn/llvm-gcc/gcc/llvm-backend.cpp: In function 'void
> llvm_initialize_b
> ackend()':
> /home/ang/svn/llvm-gcc/gcc/llvm-backend.cpp:455: error:
> 'getClosestStaticTargetF
> orModule'
2009 Aug 29
0
[LLVMdev] [Cygwin] llvm-gcc-4 bug - popcountsi2.o assertion ""V == V2 && "Didn't find key?""
2009/8/28 Aaron Gray <aaronngray.lists at googlemail.com>
> 2009/8/28 Anton Korobeynikov <anton at korobeynikov.info>
>
>> Hello, Aaron
>>
>> > -c /home/ang/svn/llvm-gcc-coff/gcc/libgcc2.c -o libgcc/./_popcountsi2.o
>> > assertion "V == V2 && "Didn't find key?"" failed: file
>> >
2009 Jul 02
2
[LLVMdev] [Cygwin] Cygwin is broken again
> Hi Aaron,
>
> Aaron Gray <aaronngray.lists <at> googlemail.com> writes:
>
>> unrecognized option '--enable-runtime-pseudo-relocs'
>
> Interesting.
> Does libCompilerDriver.dll link w/o '--enable-runtime-pseudo-relocs'?
I have not tried as of yet.
> If I understand correctly, this bug makes it impossible to produce
> loadable
>
2008 Jul 30
2
[LLVMdev] More llvm-gcc build breakage
Not sure if that's related, but we had two failures last night as well:
MacOS/Universal build failed on rev 54197, when building the x86->ppc
cross:
cc1: warnings being treated as errors
/Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning: no
previous prototype for 'outermost_tinst_level'
make[2]: *** [cp/pt.o] Error 1
MingW failed on rev 54208:
2009 Jul 02
0
[LLVMdev] OCAML and ocamldoc requirements on building andinstalling LLVM
On Jul 2, 2009, at 1:27 PM, Aaron Gray wrote:
>> On Thu, Jul 2, 2009 at 11:46 AM, Aaron
>> Gray<aaronngray.lists at googlemail.com> wrote:
>>> Jon,
>>>
>>> LLVM seems to be now dependant by default on OCAML and ocamldoc.
>>> Can you
>>> please change this so OCAML is only built and enabled when an
>>>
2009 Jul 18
2
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
I get :-
---------- Functions ----------
llvm.memcpy.i64
Mangled name = llvm.memcpy.i64
DefaultVisibility
ExternalLinkage - Externally visible.
my_memcpy
Mangled name = my_memcpy
DefaultVisibility
ExternalLinkage - Externally visible.
my_memcpy2
Mangled name =
2009 Aug 28
2
[LLVMdev] [Cygwin] llvm-gcc-4 bug - popcountsi2.o assertion ""V == V2 && "Didn't find key?""
2009/8/28 Anton Korobeynikov <anton at korobeynikov.info>
> Hello, Aaron
>
> > -c /home/ang/svn/llvm-gcc-coff/gcc/libgcc2.c -o libgcc/./_popcountsi2.o
> > assertion "V == V2 && "Didn't find key?"" failed: file
> > "/home/ang/svn/llvm-coff/
> > This is familiar but I cannot remember whether it got fixed or not now. I
>