From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: pgilliam@us.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] update gdb.base/shreloc.exp to use new shared library infrastructure
Date: Sun, 15 May 2005 19:44:00 -0000 [thread overview]
Message-ID: <20050515183621.GA16399@nevyn.them.org> (raw)
In-Reply-To: <1114922131.42745c938ed3a@imap.linux.ibm.com>
On Sun, May 01, 2005 at 12:35:31AM -0400, Wu Zhou wrote:
> > > Can we fix the testcase instead of adding -qdbxextra, by making the
> > > variable referenced? Other compilers do the same optimization, and
> > > some of them don't have a handy option to preserve the variable.
> > >
> >
> > Is it ok to change the following lines in shreloc1.c/shreloc2.c from:
> >
> > ATTRIBUTES void fn_1 (int unused) { }
> > ATTRIBUTES void fn_2 (int unused) { }
> >
> > to:
> >
> > ATTRIBUTES void fn_1 (int refered) { static_var_1 = refered; }
> > ATTRIBUTES void fn_2 (int refered) { static_var_2 = refered; }
> >
> > Please comments. Thanks.
>
> Here goes the revised patch. Wishing that it will not get mangled any
> more. Please review and comments.
>
> 2005-05-01 Paul Gilliam <pgilliam@us.ibm.com>
> Wu Zhou <woodzltc@cn.ibm.com>
>
> * gdb.base/shreloc.exp: Use gdb_compile_shlib. Add support for
> IBM's xlc compiler.
> * gdb.base/shreloc1.c: Refer variable static_var_1 in fn_1.
> * gdb.base/shreloc2.c: Refer variable static_var_2 in fn_2.
Sorry about the delay. This patch is OK, but please change two things
for me before you commit it: the correct term here is "reference"
rather than "refer", and the ChangeLog entry should show where the
changes take place. Like so:
* gdb.base/shreloc.exp: Use gdb_compile_shlib. Add support for
IBM's xlc compiler.
* gdb.base/shreloc1.c (fn_1): Reference variable static_var_1.
* gdb.base/shreloc2.c (fn_2): Reference variable static_var_2.
So with that changelog, and "refered" changed to "referenced" in the
patch, it is OK to commit.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-15 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 4:36 Wu Zhou
2005-05-15 19:44 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-18 3:20 Wu Zhou
2005-05-17 15:15 Wu Zhou
2005-05-18 1:50 ` Daniel Jacobowitz
2005-05-17 13:32 Wu Zhou
2005-05-17 14:11 ` Daniel Jacobowitz
2005-05-09 6:28 Wu Zhou
2005-05-01 4:45 Wu Zhou
2005-05-01 4:19 Wu Zhou
2005-05-01 4:28 ` Daniel Jacobowitz
2005-04-13 17:14 Paul Gilliam
2005-04-14 19:23 ` Daniel Jacobowitz
2005-04-15 19:41 ` Paul Gilliam
2005-04-20 0:31 ` Paul Gilliam
2005-04-27 15:58 ` Daniel Jacobowitz
2005-04-29 23:15 ` Paul Gilliam
2005-04-30 9:06 ` Wu Zhou
2005-04-30 18:33 ` Daniel Jacobowitz
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=20050515183621.GA16399@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.com \
--cc=woodzltc@cn.ibm.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