From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gdb-patches@sourceware.org, gcc@gcc.gnu.org
Subject: Re: [GCC PR55056] Re: [RFC patch] testsuite: Workaround issues with GCC 4.8.0pre + gdb.trace new KFAIL
Date: Fri, 14 Jun 2013 14:24:00 -0000 [thread overview]
Message-ID: <20130614133849.GA12925@host2.jankratochvil.net> (raw)
In-Reply-To: <87r4g4vo94.fsf@kepler.schwinge.homeip.net>
On Fri, 14 Jun 2013 15:02:47 +0200, Thomas Schwinge wrote:
> On Sun, 3 Feb 2013 18:27:21 +0100, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > gdb/testsuite/
> > 2013-02-02 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > Workaround GCC PR debug/55056 and GDB PR server/15081.
> > * gdb.base/restore.c (caller3): Protect l1 by GCC_PR_55056 #ifdef.
> > (caller4): Protect l1 and l2 by GCC_PR_55056 #ifdef.
> > (caller5): Protect l1, l2 and l3 by GCC_PR_55056 #ifdef.
> > * gdb.base/restore.exp: New variable opts. Test caller3, caller4 and
> > caller5 for l1, l2 and l3. New prepare_for_testing.
> > * gdb.base/store.c (wack_longest, wack_float, wack_double)
> > (wack_doublest): Protect l and r by GCC_PR_55056 #ifdef.
> > * gdb.base/store.exp: New variable opts. Test longest, float, double
> > and doublest functions for l and r. New prepare_for_testing.
> > * gdb.trace/collection.c (reglocal_test_func): Protect locf and locd by
> > GCC_PR_55056 #ifdef. Protect locar by GDB_PR_15081 #ifdef.
> > * gdb.trace/unavailable.c: Likewise.
> > * gdb.trace/collection.exp: New variable opts. Test reglocal_test_func
> > for locf, locd and locar. New prepare_for_testing.
> > (gdb_collect_locals_test): Increase list size to 43.
> > * gdb.trace/unavailable.exp: Likewise.
>
> As far as I can tell, no consensus has yet been reached about the
> approach to fix this issue discussed in this thread. (I have not looked
> at the proposed patch in detail.)
I have found now I posted the testsuite workaround for GDB
http://sourceware.org/ml/gdb-patches/2013-01/msg00688.html
but it has never been checked-in (neither in Fedora) which explains why you
see PASS->FAIL (which I also see on Fedora 19).
Jan
next prev parent reply other threads:[~2013-06-14 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 20:27 Jan Kratochvil
2013-01-28 19:57 ` Yao Qi
2013-01-29 18:16 ` Jan Kratochvil
[not found] ` <20130202092240.GA24458@host2.jankratochvil.net>
2013-02-03 17:27 ` Jan Kratochvil
2013-06-14 13:39 ` [GCC PR55056] " Thomas Schwinge
2013-06-14 14:24 ` Jan Kratochvil [this message]
2014-09-09 21:17 ` Doug Evans
2014-09-10 20:29 ` Jan Kratochvil
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=20130614133849.GA12925@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thomas@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).