From: Tom Tromey <tromey@redhat.com>
To: "Andrew Burgess" <aburgess@broadcom.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb.base/code_elim.exp - empty bss issue.
Date: Fri, 30 Aug 2013 16:26:00 -0000 [thread overview]
Message-ID: <87y57jm9gj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5220B60D.2090807@broadcom.com> (Andrew Burgess's message of "Fri, 30 Aug 2013 16:11:09 +0100")
>>>>> "Andrew" == Andrew Burgess <aburgess@broadcom.com> writes:
Andrew> I could fix this by either:
[...]
Andrew> 3. Force the test to generate some .bss content.
Andrew> I chose option #3 but would be happy to rewrite to any of the other
Andrew> options if they were prefered.
I think your choice is fine.
Andrew> 2013-08-30 Andrew Burgess <aburgess@broadcom.com>
Andrew> * gdb.base/code_elim1.c (my_bss_symbol): New variable added.
Andrew> (my_static_symbol): Add comment.
Andrew> (main): Reference my_bss_symbol.
Ok.
Tom
next prev parent reply other threads:[~2013-08-30 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 15:11 Andrew Burgess
2013-08-30 16:26 ` Tom Tromey [this message]
2013-08-30 16:36 ` Andrew Burgess
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=87y57jm9gj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aburgess@broadcom.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).