From: Michael Chastain <mec.gnu@mindspring.com>
To: zack@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: testsuite fixes for bleeding edge gcc
Date: Thu, 14 Oct 2004 12:04:00 -0000 [thread overview]
Message-ID: <416E6B8F.nail1FK2IQHOI@mindspring.com> (raw)
In-Reply-To: <87brf5n3c4.fsf@codesourcery.com>
Hi Zack!
> Current development versions of GCC are substantially pickier about
> "built-in" library functions being properly declared, which causes a
> large number of GDB testsuite failures.
Yes.
> The appended patch adds all the missing declarations to the 6.2-branch
> version of the testsuite. I haven't tried mainline. Thoughts?
Except for gdb.mi/gdb701, these are all fixed in gdb HEAD.
Also fixed in gdb HEAD are gdb.thread/*.exp, plus two tests
that check the gcc version number that needed 'gcc-4-*'.
gdb_6_2-branch is dead. Andrew is going to create gdb_6_3-branch
in a few more days or so.
If you really do have a need for it, I could merge the whole test suite
from HEAD to gdb_6_2-branch. I stopped testing gdb_6_2-branch just
recently, but before I stopped, I was regularly testing gdb from the
branch with the test suite from gdb HEAD.
Michael
next prev parent reply other threads:[~2004-10-14 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 7:53 Zack Weinberg
2004-10-14 12:04 ` Michael Chastain [this message]
2004-10-14 16:59 ` Zack Weinberg
2004-10-14 18:55 ` Michael Chastain
2004-10-14 21:32 ` Zack Weinberg
2004-10-14 19:14 ` Andrew Cagney
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=416E6B8F.nail1FK2IQHOI@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=zack@codesourcery.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