Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Laurent GUERBY <laurent@guerby.net>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: GDB <gdb@sourceware.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: GDB 6.8 fatal warning when compiled with GCC trunk 4.4  (testsuite in parallel?)
Date: Sat, 28 Feb 2009 16:49:00 -0000	[thread overview]
Message-ID: <1235839781.11347.520.camel@localhost> (raw)
In-Reply-To: <8ac60eac0902280806k3dc17152k543d99ae7dda6875@mail.gmail.com>

On Sat, 2009-02-28 at 08:06 -0800, Paul Pluzhnikov wrote:
> On Sat, Feb 28, 2009 at 6:18 AM, Laurent GUERBY <laurent@guerby.net> wrote:
> 
> > FYI GDB 6.8 fails to build when compiled with GCC trunk (4.4 not
> > released yet) because of a new warning:
> 
> Thanks for reporting this.
> 
> AFAICT, current GDB CVS Head compiles fine with GCC trunk.
> Could you confirm that?

Yes I confirm GDB HEAD builds fine with GCC trunk, on compile
farm gcc17 (bi-quad x86_64):

guerby@gcc17:~/build-gdb$ gcc --version
gcc (GCC) 4.4.0 20090228 (experimental) [trunk revision 144486]
guerby@gcc17:~/build-gdb$ ../gdb-head/configure --prefix=/n/17/guerby/install-gdb-20080228 --disable-nls
...
guerby@gcc17:~/build-gdb$ time make -j 8; echo $?
...
make[1]: Leaving directory `/home/guerby/build-gdb'

real	1m18.425s
user	4m23.184s
sys	0m38.850s
0

It looks like GDB make -k check is not parallelized so it will take
a while more to have testresults :). 

Jakub contributed last year some Makefile smartness to parallelize make
check for GCC may be the same kinf of trick would work for GDB since I
see many subtargets in gdb/Makefile.in?

Laurent



  parent reply	other threads:[~2009-02-28 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 14:18 GDB 6.8 fatal warning when compiled with GCC trunk 4.4 Laurent GUERBY
2009-02-28 16:07 ` Paul Pluzhnikov
2009-02-28 16:29   ` Joel Sherrill
2009-02-28 16:49   ` Laurent GUERBY [this message]
2009-02-28 17:16     ` Laurent GUERBY

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1235839781.11347.520.camel@localhost \
    --to=laurent@guerby.net \
    --cc=gdb@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=ppluzhnikov@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox