similar to: [LLVMdev] Debugging with llvm-gcc/mingw doesn't seem to work

Hello, Dale > Could somebody try this on Linux and investigate any failures other > than the ones above? I'm having here (x866-32/linux): Running /home/asl/proj/llvm/llvm-gcc-4.2/src/gcc/testsuite/g ++.dg/compat/struct-layout-1.exp ... Running /home/asl/proj/llvm/llvm-gcc-4.2/src/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp ... FAIL: tmpdir-gcc.dg-struct-layout-1/t025

Can you please open a bug on bugzilla and attach the ir testcase? Your fix doesn't look right (just hiding the assertion failure) On Sep 17, 2017 10:45 AM, "Andrew Kelley via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > What do you think about this patch? > > --- a/llvm/lib/Transforms/Scalar/NewGVN.cpp > +++ b/llvm/lib/Transforms/Scalar/NewGVN.cpp > @@

Hello, Paolo. > I hope this is usefull, I'm pretty new to OS X. Well. From your example you have got the only valgrind results: ==28336== 58 bytes in 2 blocks are possibly lost in loss record 70 of 127 ==28336== at 0x4020A92: operator new(unsigned) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==28336== by 0x410010B: std::string::_Rep::_S_create(unsigned, unsigned,

Hello, Argiris > Any ideas? 1. Make sure, that you don't mix dwarf and stabs debug information. AFAIR, this can really mess the things 2. It can be, that debug information emitted is not correct. This is known open problem. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Holger. > You can find out what exactly leaks with the help of valgrind. It seems, that Paolo is on Mac OS X. No valgrind there :( -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello, Argiris > I say that because I tried the linux binaries and they have the same issue. That's strange. Debug information is more or less ok on both linux and darwin. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

LLVMers, On the way to resolving bug 122, I am committing my SymbolTable rewrite. If you are working on anything that uses the SymbolTable, I suggest you read the documentation in include/llvm/SymbolTable.h. The changes I've committed reduce the use of Type::TypeTy. This static member will go away in the future, so please do not propagate new code that uses it. There is no reason to use it

Hi all, I try to build R-1.7.0 + patches. when problem arise. I start with appling the patches and second configure and make. Any ideas whats wrong (wrong compiler wrong make version or missing an essential library...) /Ulf D heres the log: **** cut************ making method_meta_data.d from method_meta_data.c making slot.d from slot.c making class_support.d from class_support.c making tests.d

Dear all, I am trying to install rgdal from source on a Mac OS 10.4.11. I installed GDAL and PROJ as frameworks so the installation does not work unless I explicitly state where the GDAL and PROJ libraries are. I tried: R CMD INSTALL rgdal_0.5-25 --configure-args=--with-proj-include=/Library/Frameworks/PROJ.framework/unix/include --with-proj-lib=/Library/Frameworks/PROJ.framework/unix/lib but I

Hi all, Perhaps this in an inappropriate post, but I've found a bug in proj I'd like to track down a bit further before making a formal bug report. The example below shows the problem, if you change the rownames proj fails. The problem seems to be that there is a mismatch in the rownames in the qr objects constructed by aov and the rownames that proj is expecting them to have.

Hello, all. Just found this file in my e-mail atchive, hope it will be useful for somebody. ===cut=here=== Some small rules: 1) No blankspace in the paths to the top-level directories. 2) Add paths to binaries to your system PATH variable. 3) Use short paths to top-level directories. 1. Some checks & preparations. 1) Be sure, that you're using right make version: $ make

Hi Erick, On Thu, 2006-12-07 at 23:31 -0800, Erick Tryzelaar wrote: > Hello, > > I'm updating the macports build of llvm, and I'm running into an issue > trying to stage llvm into a temporary directory. It builds fine, but > when I try to install it into a temporary location, it insists on > installing into the final location. Okay. > The only reference I saw

# I am sure that I could be more efficient than this but how? Thanks in advance. #GPS in Decimal Degrees in the form longitude latitude RM215 <- matrix(c(-82.1461363, 33.5959109), nrow=1) SC <- matrix(c(-82.025888, 33.606454), nrow=1) RM202 <- matrix(c(-81.9906723, 33.5027653), nrow=1) RM198 <- matrix(c(-81.926823, 33.4634678), nrow=1) HC <- matrix(c(-81.920505, 33.46192), nrow=1)

I'm hoping someone can help me. I have downloaded the proj4R.zip and under my version of R (2.3.1) I install the package from local zip file. This worked great. I then type library(proj4R) to load the library and I get the error: Error in library(proj4R) : 'proj4R' is not a valid package -- installed < 2.0.0? I have read through the install documentation and have downloaded and

Reid Spencer wrote: > Yes, but its a bit verbose. The variables that control this are all > defined in the Makefile.config file. The variables are: > > PROJ_prefix := /proj/llvm/install-1 > PROJ_bindir := /proj/llvm/install-1/bin > PROJ_libdir := /proj/llvm/install-1/lib > PROJ_datadir := /proj/llvm/install-1/share > PROJ_docsdir :=

Hi, Here are the steps to reproduce the debugging issue: -create test.c: int main() { return 0; } -llvm-gcc -g test.c -o test.exe -gdb test.exe -(gdb) break test.c:3 >> No line 3 in file "test.c". This is with the llvm-2.3-x86-mingw32 binaries and gdb-6.8-mingw-3. Any ideas? -Argiris

On Thu, 16 Nov 2006, Tanya M. Lattner wrote: >> * I don't think this is ready for release. In particular the llvm-gcc4 >> binary >> seg faults on FC 5 for most of llvm-test programs. >> * I'm going to re-try without using the binaries and building >> everything from scratch. > > Does llvm-gcc4 seg fault for make check? I've done extensive

First, thanks for testing this! > Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) > > HIGH LEVEL COMMENTS > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > that be llvm-1.9? We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9. > * LLVM was built in Release mode

Anton Korobeynikov <asl at math.spbu.ru> writes: [snip] > 2) Problem: Complains about gthr-default.h file. > Resolution: Grab gcc/gcc/gthr-win32.h file and copy it to gthr-default.h ... so --enable-threads=win32 is broken... good to know. > 3) Problem: Complains about "CL_ObjCXX" and simular ("CL_") during > compilation

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have