From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Make cu/tu functions in dwarf.exp take a list of options
Date: Fri, 17 May 2013 18:04:00 -0000 [thread overview]
Message-ID: <871u95qy90.fsf@fleche.redhat.com> (raw)
In-Reply-To: <yjt2obc9frdv.fsf@ruffy.mtv.corp.google.com> (Doug Evans's message of "Fri, 17 May 2013 10:27:56 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> Ok to check in?
Doug> Regression tested on amd64-linux.
Looks good to me.
Doug> 2013-05-17 Doug Evans <dje@google.com>
Doug> * lib/dwarf.exp (Dwarf): New variable _abbrev_section.
Doug> (_handle_DW_TAG): Use it.
Doug> (cu): Replace parameters is_64, version, addr_size with options.
Doug> All callers updated. Add Fission support.
I thought we were supposed to list all the changed files, even in this
case. If not, it would be nice to know, so I can stop doing that in the
future.
Tom
next prev parent reply other threads:[~2013-05-17 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 17:28 Doug Evans
2013-05-17 18:04 ` Tom Tromey [this message]
2013-05-17 18:20 ` Doug Evans
2013-05-20 5:40 ` Joel Brobecker
2013-05-20 16:42 ` Doug Evans
2013-05-20 22:09 ` Doug Evans
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=871u95qy90.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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