[llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Chris Lattner
Changes in directory llvm/test/DebugInfo: 2006-11-06-StackTrace.cpp updated: 1.11 - 1.12 --- Log message: fix failure on ahs3's tester --- Diffs of the changes: (+3 -1) 2006-11-06-StackTrace.cpp |4 +++- 1 files changed, 3 insertions(+), 1 deletion(-) Index:

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Jeff Cohen
Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. Chris Lattner wrote: Changes in directory llvm/test/DebugInfo: 2006-11-06-StackTrace.cpp updated: 1.11 - 1.12 --- Log message: fix failure on ahs3's tester

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Chris Lattner
On May 5, 2007, at 2:03 PM, Jeff Cohen wrote: Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. No, I'm not sure. A better question is: why is this ppc specific? :) -Chris Chris Lattner wrote: Changes in

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Jeff Cohen
Chris Lattner wrote: On May 5, 2007, at 2:03 PM, Jeff Cohen wrote: Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. No, I'm not sure. A better question is: why is this ppc specific? :) -Chris On my

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Chris Lattner
On May 5, 2007, at 2:49 PM, Jeff Cohen wrote: Chris Lattner wrote: On May 5, 2007, at 2:03 PM, Jeff Cohen wrote: Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. No, I'm not sure. A better question is:

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Anton Korobeynikov
Ok, then it really is failing. Same here. This is strange, however I haven't tested debug information on C++ programs. Will try to look. -- With best regards, Anton Korobeynikov. Faculty of Mathematics Mechanics, Saint Petersburg State University.

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Jeff Cohen
Chris Lattner wrote: On May 5, 2007, at 2:49 PM, Jeff Cohen wrote: Chris Lattner wrote: On May 5, 2007, at 2:03 PM, Jeff Cohen wrote: Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. No, I'm not sure. A

Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp

2007-05-05 Thread Anton Korobeynikov
Jeff, This is the output on my machine. It looks better than when I last looked at it, but still leaves a lot to be desired. Could you please send me output from your native compiler. Something like 'gcc -g -O0 -S -dA foo.c' should be enough. -- With best regards, Anton Korobeynikov.

[llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp 2006-11-20-GlobalSymbols.cpp 2006-11-30-NoCompileUnit.cpp 2006-11-30-Pubnames.cpp dg.exp

2007-04-15 Thread Reid Spencer
Changes in directory llvm/test/DebugInfo: 2006-11-06-StackTrace.cpp updated: 1.10 - 1.11 2006-11-20-GlobalSymbols.cpp updated: 1.1 - 1.2 2006-11-30-NoCompileUnit.cpp updated: 1.2 - 1.3 2006-11-30-Pubnames.cpp updated: 1.5 - 1.6 dg.exp updated: 1.2 - 1.3 --- Log message: For PR1319: