From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com,
Daniel Jacobowitz <drow@mvista.com>, Jim Blandy <jimb@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>
Subject: Re: [rfa+6.1]: Fix gcc 3.4 regression in gdb.cp/namespace.exp
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <16471.25753.503491.536866@localhost.redhat.com> (raw)
In-Reply-To: <yf2llm01u41.fsf_-_@hawaii.kealia.com>
David Carlton writes:
> On Tue, 16 Mar 2004 10:25:39 -0800, David Carlton <carlton@kealia.com> said:
>
> > So what's the correct fix here? I tend to think that the code would
> > be easier to understand if we only generated symbols while going
> > through the code in the obvious tree order (calling functions named
> > process_XXX, ideally), instead of while following various
> > cross-references (which we would only do via functions named read_XXX,
> > ideally). Is that a reasonable hope? If so, it seems like the
> > correct fix would be to change process_structure_scope to call
> > process_die on all of its children, whether or not the current die is
> > a declaration. I'll play around with a patch like that - it should be
> > safe, I hope, since process_structure_scope is only called from
> > process_die, so we shouldn't be generating symbols twice.
>
> Here's a patch implementing that. It looks messier than it is - all I
> did was move the loop over children before the test for whether or not
> we're a declaration. I've tested it on mainline with
> i686-pc-linux-gnu, DWARF-2, and four different GCC versions; no new
> regressions, and it fixes the regression in question. Is it okay to
> commit? If so, is it also okay for 6.1 (assuming that the tests pass
> there as well, which I'm about to start checking)?
Fine, yes.
Maybe Daniel should have a look too?
elena
WARNING: multiple messages have this Message-ID
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com,
Daniel Jacobowitz <drow@mvista.com>, Jim Blandy <jimb@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>
Subject: Re: [rfa+6.1]: Fix gcc 3.4 regression in gdb.cp/namespace.exp
Date: Tue, 16 Mar 2004 20:39:00 -0000 [thread overview]
Message-ID: <16471.25753.503491.536866@localhost.redhat.com> (raw)
Message-ID: <20040316203900.x-4ll1GjG2CBNlACjrg56x7WssLx0L7dyNjTCBRffto@z> (raw)
In-Reply-To: <yf2llm01u41.fsf_-_@hawaii.kealia.com>
David Carlton writes:
> On Tue, 16 Mar 2004 10:25:39 -0800, David Carlton <carlton@kealia.com> said:
>
> > So what's the correct fix here? I tend to think that the code would
> > be easier to understand if we only generated symbols while going
> > through the code in the obvious tree order (calling functions named
> > process_XXX, ideally), instead of while following various
> > cross-references (which we would only do via functions named read_XXX,
> > ideally). Is that a reasonable hope? If so, it seems like the
> > correct fix would be to change process_structure_scope to call
> > process_die on all of its children, whether or not the current die is
> > a declaration. I'll play around with a patch like that - it should be
> > safe, I hope, since process_structure_scope is only called from
> > process_die, so we shouldn't be generating symbols twice.
>
> Here's a patch implementing that. It looks messier than it is - all I
> did was move the loop over children before the test for whether or not
> we're a declaration. I've tested it on mainline with
> i686-pc-linux-gnu, DWARF-2, and four different GCC versions; no new
> regressions, and it fixes the regression in question. Is it okay to
> commit? If so, is it also okay for 6.1 (assuming that the tests pass
> there as well, which I'm about to start checking)?
Fine, yes.
Maybe Daniel should have a look too?
elena
next prev parent reply other threads:[~2004-03-16 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yf2brmx3aia.fsf@hawaii.kealia.com>
[not found] ` <yf2ptbc1wf0.fsf@hawaii.kealia.com>
2004-03-19 0:09 ` David Carlton
2004-03-16 19:15 ` David Carlton
2004-03-19 0:09 ` Elena Zannoni [this message]
2004-03-16 20:39 ` Elena Zannoni
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-16 22:28 ` Daniel Jacobowitz
2004-03-16 22:45 ` David Carlton
2004-03-19 0:09 ` David Carlton
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=16471.25753.503491.536866@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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