Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] debug info for global variables when optimising"
2009 Jun 01
0
[LLVMdev] debug info for global variables when optimising
On May 29, 2009, at 6:24 AMPDT, Jay Foad wrote:
> I see that llvm-gcc now has some support for generating debug info
> when optimising - thanks!
>
> However, it still doesn't generate debug info for global variables
> when optimising. Is there any reason for this? With the attached
> patch, the whole test suite passes for me with TEST=ipodbgopt.
The reason is given in the
2009 Jun 03
1
[LLVMdev] debug info for global variables when optimising
> TEST=ipodbgopt currently runs through -strip-debug-declare immediately,
> which would hide such cases. Try it with that flag removed and I bet you'll
> see some failures.
Yes, thanks, I hadn't noticed the -strip-debug-declare.
Incidentally I only "see" the failures because some "TEST-FAIL"
messages whizz up and off the screen. The actual "make
2009 May 29
2
[LLVMdev] make TEST=ipodbgopt in sqlite3: problem with TCLSH
On Linux, when I run "make TEST=ipodbgopt" in
MultiSource/Applications/sqlite3 I get:
make[4]: Entering directory
`/home/foad/llvm/poo/build/test-suite/MultiSource/Applications/sqlite3'
Compiling shell.c to Output/shell.bc
/home/foad/svn/llvm-project/test-suite/trunk/MultiSource/Applications/sqlite3/speedtest.tcl
make[4]: execvp:
2009 May 29
0
[LLVMdev] make TEST=ipodbgopt in sqlite3: problem with TCLSH
On 2009-05-29 15:55, Jay Foad wrote:
> On Linux, when I run "make TEST=ipodbgopt" in
> MultiSource/Applications/sqlite3 I get:
>
> make[4]: Entering directory
> `/home/foad/llvm/poo/build/test-suite/MultiSource/Applications/sqlite3'
> Compiling shell.c to Output/shell.bc
> /home/foad/svn/llvm-project/test-suite/trunk/MultiSource/Applications/sqlite3/speedtest.tcl
2009 Jul 09
1
[LLVMdev] Source file information.
Hi David,
On Thu, Jul 9, 2009 at 10:26 AM, David Greene<dag at cray.com> wrote:
> On Thursday 09 July 2009 10:01, John Criswell wrote:
>> Dear All,
>>
>> To add to this, what you want to do is find the appropriate debug stop
>> point intrinsic and then use it to look up the information for that
>> instruction.
>
> Ick. So line number information is
2009 Apr 23
3
[LLVMdev] support for division by constant in APInt
In lib/CodeGen/SelectionDAG/TargetLowering.cpp there are some
functions magic() and magicu() that support optimising division by a
constant. I'd like to use these functions in an LLVM FunctionPass that
I'm working on. The attached patch moves these functions out of
TargetLowering.cpp and into the APInt class, so that I can reuse them
in my pass. What do you think?
It looks to me like
2009 Oct 20
2
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 5:49 AM, Jay Foad wrote:
>> To test clang:
>> 1) Compile llvm and clang from source.
>
> LLVM fails to build for me on Cygwin. I get:
>
Does TOT build? If not, please file a bug.
Unfortunately Cygwin is not in our release criteria. I'd like to have
a buildbot running (if there is not one already) and then get someone
to qualify it for the
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
> To test clang:
> 1) Compile llvm and clang from source.
LLVM fails to build for me on Cygwin. I get:
make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime'
make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile'
llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC)
llvm[2]: Compiling BlockProfiling.c for Release build (PIC)
llvm[2]:
2009 Oct 20
3
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote:
> 2009/10/20 Tanya Lattner <lattner at apple.com>:
>>
>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote:
>>
>>>> To test clang:
>>>> 1) Compile llvm and clang from source.
>>>
>>> LLVM fails to build for me on Cygwin. I get:
>>>
>>
>> Does TOT build? If not,
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
2009/10/20 Tanya Lattner <lattner at apple.com>:
>
> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote:
>
>>> To test clang:
>>> 1) Compile llvm and clang from source.
>>
>> LLVM fails to build for me on Cygwin. I get:
>>
>
> Does TOT build? If not, please file a bug.
No. Theres the runtime install bug (below), and llvm-gcc has a bug
that I
2009 Oct 20
0
[LLVMdev] [cfe-dev] 2.6 pre-release2 ready for testing
2009/10/20 Tanya Lattner <lattner at apple.com>:
>
> On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote:
>
>> 2009/10/20 Tanya Lattner <lattner at apple.com>:
>>>
>>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote:
>>>
>>>>> To test clang:
>>>>> 1) Compile llvm and clang from source.
>>>>
>>>> LLVM
2009 Apr 17
15
[LLVMdev] mingw build problems
I'm trying to cross-compile LLVM with build=, host=target=. I'm using
the following packages from Debian lenny:
mingw32 4.2.1.dfsg-1
mingw32-binutils 2.18.50-20080109-1
mingw32-runtime 3.13-1
The first problem I hit was when I configured with CC, CXX, AR and
RANLIB set to mingw cross-tools, but forgot to specify NM as well.
This resulted in a load of warnings that scrolled off the
2014 May 13
4
[LLVMdev] s/ComputeMaskedBits/ComputeKnownBits/g ?
I've always found the name ComputeMaskedBits a bit unintuitive, and
since r154011 it's even worse because there is no masking going on
whatsoever:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120402/140280.html
Is there any appetite for a global rename to ComputeKnownBits? Or any
other better names?
Thanks,
Jay.
2010 Jan 07
2
[LLVMdev] configuring llvm-gcc 2.6 for mips
Hi,
If I configure llvm-gcc 2.6 with --target=mips or --target=mips-elf, I get:
c++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall
-Wwrite-strings -pedantic -Wno-long-long -Wno-variadic-macros
-Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -Wno-unused
-DTARGET_NAME=\"mips-elf\" -frandom-seed=0 -I. -I.
-I/home/foad/toolchain/llvm/llvm-gcc/gcc
2009 Feb 12
4
[LLVMdev] problems running test suite (-mllvm -disable-llvm-optzns)
I'm trying to run some of the test suite using the instructions here:
http://llvm.org/docs/TestingGuide.html#quicktestsuite
I've built llvm myself, but I'm using pre-built binaries of llvm-gcc
(from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz).
Here's what happens:
foad at debian:~/svn/llvm-project/test-suite/trunk$ ./configure
2012 Feb 13
2
[LLVMdev] We need better hashing
On 13 February 2012 09:22, Jay Foad <jay.foad at gmail.com> wrote:
> Would it be possible to use CityHash instead for strings?
>
> http://code.google.com/p/cityhash/
Incidentally there was talk of using CityHash for LLVM's StringMap
last year, but I don't think it ever came to anything:
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-April/014656.html
Jay.
2010 Aug 04
1
Optimising the Rsync algorithm for speed by reverting to MD4 hashing
Hi,
From v3.0.0 onwards the hash function implemented by Rsync was changed from MD4 to MD5 (http://rsync.samba.org/ftp/rsync/src/rsync-3.0.0-NEWS). My understanding is that MD5 is a more secure, slower version of MD4 but I am not convinced that the added security of MD5 would alone have merited the change from MD4 (particularly since MD4 is ~30% faster than MD5). I wonder if I am missing other
2009 May 15
3
[LLVMdev] "Processed value not in any map!" failures
When I build LLVM with ENABLE_EXPENSIVE_CHECKS=1, make check fails:
Running /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/dg.exp ...
FAIL: /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/2007-05-14-InlineAsmCstCrash.ll
Failed with signal(SIGABRT) at line 1
while running: llvm-as <
/home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/2007-05-14-InlineAsmCstCrash.ll
| llc
2015 Nov 12
4
Fwd: asan for allocas on powerpc64
(Resending with the correct mailing list address.)
Hi,
Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for
powerpc64. I've had a look at why it doesn't work. I think the only
problem is in the call to __asan_allocas_unpoison that is inserted at
the end of the "for" loop (just before a stackrestore instruction).
The call function is created something like this
2011 May 06
8
[LLVMdev] nightly test suite failure: ms_struct-bitfield-init-1.c
Hi,
I've just tried to run the test-suite, for the first time in ages. It
stops rather abruptly with:
$ make TEST=nightly report report.html
/home/jay/llvm/local/bin/llvm-gcc
-I/home/jay/llvm/gitobjdir/projects/test-suite/SingleSource/UnitTests
-I/home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests
-I/home/jay/git/llvm/projects/test-suite/include -I../../include