From: Joseph Myers <joseph@codesourcery.com>
To: Caroline Tice <cmtice@google.com>
Cc: Eric Christopher <echristo@google.com>,
Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>,
Caroline Tice via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Update testsuite mechanism to allow object files as source files.
Date: Thu, 16 Jul 2020 20:35:41 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2007162034130.19299@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CABtf2+TZdzcAfxNrkVtZ-4ajGqMRC+PrYZvwcOJ+=hebNTFctQ@mail.gmail.com>
On Thu, 16 Jul 2020, Caroline Tice via Gdb-patches wrote:
> The command used to generate the .object file is added in the comments
> of the updated testcase in the patch I attached to the first message
> in this thread (in the file
> gdb/testsuite/gdb.dwarf2/dw5-rnglist-test.exp. I did not include the
> compiler version information in those comments, but I can certainly
> update it to do so.
Note that it's best for the compiler for this sort of thing to be an
unmodified upstream version - not a distribution version. Cf. the issues
we have with people checking in configure scripts generated by
distribution version of autoconf, which are not the same as generated by
upstream autoconf.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-07-16 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 16:50 Caroline Tice
2020-07-16 17:21 ` Andrew Burgess
2020-07-16 18:07 ` Caroline Tice
2020-07-16 18:29 ` Andrew Burgess
2020-07-16 17:33 ` Joseph Myers
2020-07-16 18:13 ` Caroline Tice
2020-07-16 18:47 ` Andrew Burgess
2020-07-16 20:35 ` Joseph Myers [this message]
2020-07-16 20:12 ` Tom Tromey
2020-07-16 21:10 ` Caroline Tice
2020-07-16 21:16 ` Eric Christopher
2020-07-17 9:48 ` Andrew Burgess
2020-07-17 16:05 ` Caroline Tice
2020-07-17 9:43 ` Andrew Burgess
2020-07-17 17:45 ` Tom Tromey
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=alpine.DEB.2.21.2007162034130.19299@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=cmtice@google.com \
--cc=echristo@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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