FAQ

Smoking different gcc versions

Bram
Apr 14, 2008 at 8:56 pm
Hello,


I'm currently playing with smoking different gcc versions.

My question: what would the best approach for this be?

I ran a smoke using a configuration file with:

=
-Dcc='ccache gcc'
-Dcc='ccache /tmp/GCC/D/bin/gcc'

The output in mktest.rpt:

darkstar: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel
2400MHz) (i686/4 cpu)
on linux - 2.6.22-smp [slackware]
using ccache gcc version 4.1.2
smoketime 26 minutes 14 seconds (average 13 minutes 7 seconds)

...

33662 Configuration (common) none
----------- ---------------------------------------------------------
O O - - -Dcc='ccache gcc'
O O - - -Dcc='ccache /tmp/GCC/D/bin/gcc'
+----- PERLIO = perlio -DDEBUGGING
+------- PERLIO = stdio -DDEBUGGING
+--------- PERLIO = perlio
+----------- PERLIO = stdio


The output in mktest.out:

...
Configuration: -Dusedevel -Dcc='ccache gcc'
------------------------------------------------------------------------------

Compiler info: ccache gcc version 4.1.2
...

Configuration: -Dusedevel -Dcc='ccache /tmp/GCC/D/bin/gcc'
------------------------------------------------------------------------------

Compiler info: ccache /tmp/GCC/D/bin/gcc version 4.2.3
...


The header in mktest.rpt only lists 4.1.2 and not 4.2.3.

This brings me to my question:

What would the prefered solution be?
a) running multiple smokes - one for each versions of gcc?
b) A patch for the report builder to output each gcc versions? (which
would also mean patching the summary builder and so on)


(My current testing idea is to install each version of gcc and smoke it.
When that is up and running I'm also thinking of installing the gcc
snapsnots and testing those (first the gcc test, then a perl smoke). The
downside of this last one is - of course - that some builds will fail due
to unresolved/new bugs in gcc.)


Kind regards,

Bram
reply

Search Discussions

1 response

  • H.Merijn Brand at Apr 15, 2008 at 10:41 am

    On Mon, 14 Apr 2008 22:55:55 +0200, Bram wrote:

    Hello,


    I'm currently playing with smoking different gcc versions.

    My question: what would the best approach for this be?

    I ran a smoke using a configuration file with:

    =
    -Dcc='ccache gcc'
    -Dcc='ccache /tmp/GCC/D/bin/gcc'
    Please split up the reports for different compilers and/or compiler
    versions. Here' how I use it:

    --8<--- p59.sh
    :
    :
    cd /pro/3gl/CPAN/smoke
    cp MANIFEST_SKIP /pro/3gl/CPAN/perl-current/MANIFEST.SKIP

    /pro/bin/perl smokeperl.pl --nofetch --nopatch \
    -c "$CFGNAME" $continue $* > p59.log 2>&1
    cp p59.log log/p59-cc.log
    cp ../perl-current/mktest.out log/mktest-cc.out
    cp ../perl-current/mktest.rpt log/mktest-cc.rpt

    cd /pro/3gl/CPAN/perl-current
    ../ChkMANI.pl >/dev/null 2>&1

    cd /pro/3gl/CPAN/smoke
    cp MANIFEST_SKIP /pro/3gl/CPAN/perl-current/MANIFEST.SKIP

    /pro/bin/perl smokeperl.pl --nofetch --nopatch \
    -Dcc=gcc \
    -c "$CFGNAME" $continue $* > p59.log 2>&1
    cp p59.log log/p59-gcc.log
    cp ../perl-current/mktest.out log/mktest-gcc.out
    cp ../perl-current/mktest.rpt log/mktest-gcc.rpt

    rm "$LOCKFILE"
    -->8---

    ../ChkMANI.pl is like 'make distclean', but as I have several
    directories and files that deal with Configure maintainership that I do
    NOT want removed, I deal with that a bit different


    --
    H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
    using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11,
    & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org
    http://mirrors.develooper.com/hpux/ http://www.test-smoke.org
    http://www.goldmark.org/jeff/stupid-disclaimers/

Related Discussions

Discussion Navigation
viewthread | post

2 users in discussion

H.Merijn Brand: 1 post Bram: 1 post