On Sat, May 7, 2011 at 16:50, Sandeep Soni <soni.sande...@gmail.com> wrote:
> I got the build working on my machine. So preliminarily things seem to > be working. In case this merge brings our branch up to 4.7 should "gcc > -v" be showing it? It is not currently. Yes, gcc -v should show: Using built-in specs. COLLECT_GCC=bin/gcc COLLECT_LTO_WRAPPER=/usr/local/google/home/dnovillo/gimplefe/svn/native/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.7.0-gimplefe/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /home/dnovillo/gimplefe/svn/src/configure --prefix=/home/dnovillo/gimplefe/svn/native --enable-languages=gimple Thread model: posix gcc version 4.7.0-gimplefe 20110502 (trunk r173270) (experimental) (GCC) Note that to get version output, you should use --version. > Sure. I will see how dejagnu works since I have no prior experience > using it. I will try adding some testcases to the testsuite. Great. Let me know if you get stuck. In principle, you'd have to copy from gcc/testsuite/gcc.dg. Create a directory gcc/testsuite/gimple.dg and adapt gcc/testsuite/gcc.dg/dg.exp. There will be wrinkles, I'm sure. Diego.
