From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Laurent GUERBY <laurent@guerby.net>
Cc: GDB <gdb@sourceware.org>
Subject: Re: GDB 6.8 fatal warning when compiled with GCC trunk 4.4
Date: Sat, 28 Feb 2009 16:07:00 -0000 [thread overview]
Message-ID: <8ac60eac0902280806k3dc17152k543d99ae7dda6875@mail.gmail.com> (raw)
In-Reply-To: <1235830682.11347.492.camel@localhost>
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?
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-02-28 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 14:18 Laurent GUERBY
2009-02-28 16:07 ` Paul Pluzhnikov [this message]
2009-02-28 16:29 ` Joel Sherrill
2009-02-28 16:49 ` GDB 6.8 fatal warning when compiled with GCC trunk 4.4 (testsuite in parallel?) Laurent GUERBY
2009-02-28 17:16 ` GDB 6.8 fatal warning when compiled with GCC trunk 4.4 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=8ac60eac0902280806k3dc17152k543d99ae7dda6875@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=laurent@guerby.net \
/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