From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: David Blaikie <dblaikie@gmail.com>
Cc: Eric Christopher <echristo@gmail.com>,
Douglas Evans <dje@google.com>, Pedro Alves <palves@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patch] [gdb/testsuite] XFAIL under Clang tests using label debug info
Date: Fri, 06 Sep 2019 20:25:00 -0000 [thread overview]
Message-ID: <CAPTJ0XFp0nayK9d1OfZh8Qj1cPDkp8JebrPKt_jexnMBxW-NVg@mail.gmail.com> (raw)
In-Reply-To: <CAENS6EvZYobqmZLY-yQ+T97guMCEe93E56xUp8eLwq2swpbRnQ@mail.gmail.com>
On Fri, Sep 6, 2019 at 3:23 PM David Blaikie <dblaikie@gmail.com> wrote:
> On Fri, Sep 6, 2019 at 10:26 AM Christian Biesinger
> <cbiesinger@google.com> wrote:
> >
> > Thanks! So I think that requires clang 10?
>
> The fix was made last year (July 24, 2018) - so I think that means it
> should be in Clang 7.0, though I haven't tested specifically.
>
Reading is hard :( Thanks. That certainly seems long enough ago that
removing this is reasonable (but I'm not an approver)
Christian
>
> >
> > Christian
> >
> > On Thu, Sep 5, 2019 at 11:17 PM Eric Christopher <echristo@gmail.com>
> wrote:
> >>
> >> https://bugs.llvm.org/show_bug.cgi?id=14500#c3 has the relevant
> information :)
>
> Thanks Eric!
>
> >>
> >> On Thu, Sep 5, 2019, 7:48 PM Christian Biesinger via gdb-patches <
> gdb-patches@sourceware.org> wrote:
> >>>
> >>> On Thu, Sep 5, 2019 at 5:12 PM David Blaikie <dblaikie@gmail.com>
> wrote:
> >>> >
> >>> > Clang now supports labels - so I'd like to essentially revert this
> patch.
> >>>
> >>> Out of curiosity, when did clang get support for this?
> >>>
> >>> Christian
> >>>
> >>> > Is this OK?
> >>> >
> >>> >
> >>> > On Thu, Apr 24, 2014 at 8:23 PM David Blaikie <dblaikie@gmail.com>
> wrote:
> >>> > >
> >>> > > On Wed, Apr 23, 2014 at 3:03 PM, Doug Evans <dje@google.com>
> wrote:
> >>> > > > David Blaikie writes:
> >>> > > > > Clang doesn't emit debug info for labels (Clang PR14500).
> XFAIL a
> >>> > > > > bunch of GDB tests that rely on debug info for labels.
> >>> > > > >
> >>> > > > > For some reason gdb.linespec/ls-expr.exp gathered all tests
> into a
> >>> > > > > dictionary and then ran them. This made it hard to XFAIL just
> the
> >>> > > > > right tests. I refactored this to execute the tests directly,
> removing
> >>> > > > > the dictionary so I could XFAIL the right tests. Is there a
> reason it
> >>> > > > > would've been written that way? Does my patch break it in
> some way?
> >>> > > > > commit c438cb16b63292e415330f289616c4e4ecece63c
> >>> > > > > Author: David Blaikie <dblaikie@gmail.com>
> >>> > > > > Date: Sun Apr 13 11:42:02 2014 -0700
> >>> > > > >
> >>> > > > > XFAIL under Clang tests using labels
> >>> > > > >
> >>> > > > > gdb/testsuite/
> >>> > > > > * gdb.base/label.exp: XFAIL label related tests under
> Clang.
> >>> > > > > * gdb.cp/cplabel.exp: Ditto.
> >>> > > > > * gdb.linespec/ls-errs.exp: Refactor tests to execute
> directly
> >>> > > > > and XFAIL under Clang those using labels.
> >>> > > >
> >>> > > > LGTM
> >>> > > >
> >>> > > > > diff --git gdb/testsuite/ChangeLog gdb/testsuite/ChangeLog
> >>> > > > > index 730c116..b04b940 100644
> >>> > > > > --- gdb/testsuite/ChangeLog
> >>> > > > > +++ gdb/testsuite/ChangeLog
> >>> > > > > @@ -1,3 +1,9 @@
> >>> > > > > +2014-04-12 David Blaikie <dblaikie@gmail.com>
> >>> > > > > +
> >>> > > > > + * gdb.base/label.exp: XFAIL label related tests
> under Clang.
> >>> > > > > + * gdb.cp/cplabel.exp: Ditto.
> >>> > > > > + * gdb.linespec/ls-errs.exp: Refactor tests to execute
> directly and XFAIL under Clang those using labels.
> >>> > > > > +
> >>> > > >
> >>> > > > Nit: space vs tabs. Just use tabs.
> >>> > > > Plus line is longer than 80 chars.
> >>> > >
> >>> > > Thanks for the catches - fixed those up and committed in
> >>> > > c2e827ad5340fcf1735df6c77cb0311e56b985ef.
> >>> > >
> >>> > > Also refactored some of the xfails along the lines of what Pedro
> >>> > > suggested in the one test case that had several similar failures
> >>> > > (gdb.base/label.exp). If/when we fix this in Clang it might be
> worth
> >>> > > refactoring into a common function (though I'm personally not very
> >>> > > vested in keeping the test suite usable with anything other than
> ToT
> >>> > > Clang - perhaps others are).
>
next prev parent reply other threads:[~2019-09-06 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 23:26 David Blaikie
2014-04-23 22:03 ` Doug Evans
2014-04-25 3:23 ` David Blaikie
2019-09-05 22:12 ` David Blaikie
2019-09-06 2:48 ` Christian Biesinger via gdb-patches
2019-09-06 4:17 ` Eric Christopher
2019-09-06 17:26 ` Christian Biesinger via gdb-patches
2019-09-06 20:23 ` David Blaikie
2019-09-06 20:25 ` Christian Biesinger via gdb-patches [this message]
[not found] ` <CADPb22Svrkdy6eOmcY2CxYAHfmaz_vRPE8sLDrujJCjbXCFMNg@mail.gmail.com>
2019-09-06 21:19 ` David Blaikie
2014-04-24 10:42 ` Pedro Alves
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=CAPTJ0XFp0nayK9d1OfZh8Qj1cPDkp8JebrPKt_jexnMBxW-NVg@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--cc=dblaikie@gmail.com \
--cc=dje@google.com \
--cc=echristo@gmail.com \
--cc=palves@redhat.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