Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Hui Zhu <teawater@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [OB] Fix xcoffread.c build error
Date: Wed, 25 May 2011 07:21:00 -0000	[thread overview]
Message-ID: <3CE959C7-9DD8-46A7-9FAC-230C3E2DCA55@adacore.com> (raw)
In-Reply-To: <201105241727.43826.pedro@codesourcery.com>


On May 24, 2011, at 6:27 PM, Pedro Alves wrote:

[...]

> It that were possible, then why would we need fcn_aux_saved
> at all?  This is a bit hard to follow without a
> file to test with, but ISTM that fcn_aux_saved is needed because
> main_aux no longer contains what we need at the time time
> fcn_aux_saved is used (that is, we've moved to
> another symbol/aux).
> 
> Does gcc still output a warning with this for you?
> 
> Maybe Tristian can check if this doesn't break something?

I can do a sanity check if you need (please confirm), but a full regression (using AdaCore testsuite)
will be done when Joel updates our head branch.

> (I suppose fcn_aux_saved and a bunch other locals should be
> cleared somewhere, most likely after finish_block, or
> where we do the complaints.)

Your change looks safe, but as fcn_aux_saved_p is never cleared, it will catch
only if the missing PR symbol is the first one.

IMHO (and just IMHO), to get rid of the warning why not saving only the fsize field (instead of
the whole aux entry) and initialize to 0 ?

Tristan.


  parent reply	other threads:[~2011-05-25  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19  6:56 Hui Zhu
2011-05-19  9:59 ` Pedro Alves
2011-05-20  5:13   ` Hui Zhu
2011-05-24 16:28     ` Pedro Alves
2011-05-24 16:29       ` Pedro Alves
2011-05-25  7:21       ` Tristan Gingold [this message]
2011-05-25 21:01         ` Joel Brobecker

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=3CE959C7-9DD8-46A7-9FAC-230C3E2DCA55@adacore.com \
    --to=gingold@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=teawater@gmail.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