Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
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, 01 May 2005 04:19:00 -0000	[thread overview]
Message-ID: <1114921124.427458a4c9c4a@imap.linux.ibm.com> (raw)

Quoting Daniel Jacobowitz <drow@false.org>:

> This does not be long in the changelog, only in the comments.  The
> ChangeLog for this patch should look like:
> 
> 2005-04-29  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.
> 
> If you're going to post patches to this list, please find a mail client
> which does not mangle line wrapping; the patch as I received it is hard
> to read and can not be applied.

Sorry, wish that this time it is ok.

> OK, now I understand why you needed the options.  We will need
> -qstatsym; here's a better description:
> 
>   # IBM's xlc compiler does not add static variables to the ELFe symbol
>   # table by default.  We need this option to make the variables show
>   # up in "maint print msymbols".
> 
> 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.

Cheers
- Wu Zhou


             reply	other threads:[~2005-05-01  4:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01  4:19 Wu Zhou [this message]
2005-05-01  4:28 ` Daniel Jacobowitz
  -- 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:36 Wu Zhou
2005-05-15 19:44 ` 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=1114921124.427458a4c9c4a@imap.linux.ibm.com \
    --to=woodzltc@cn.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pgilliam@us.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