From: Frederic RISS <frederic.riss@st.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: Daniel Jacobowitz <drow@false.org>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Don't lose compilation directory in Dwarf2 line-tables
Date: Fri, 21 Apr 2006 17:00:00 -0000 [thread overview]
Message-ID: <1145638813.14807.1094.camel@crx549.cro.st.com> (raw)
In-Reply-To: <8f2776cb0604210946kf7c1e2br2c4c47ecbfa9322d@mail.gmail.com>
On Fri, 2006-04-21 at 09:46 -0700, Jim Blandy wrote:
> On 4/21/06, Frederic RISS <frederic.riss@st.com> wrote:
> > > - Leave the comparison loop alone, as in your last patch.
> > > - If dwarf2_start_subfile does have to start a subfile itself, always
> > > pass comp_dir as start_subfile's second argument, whether it's NULL or
> > > not (because this is what we do when calling start_symtab), and
> > > concatenate dirname, if it's non-null, with filename to get
> > > start_subfile's first argument. I think this means that 'fullname'
> > > always gets used, so you can hoist that computation and its xfree out
> > > of the 'if'.
> >
> > But then, the loop in dwarf2_start_subfile doesn't serve any purpose,
> > because the loop at the beginning of start_subfile proper will do the
> > same work. Or maybe I'm missing something?
>
> No --- I hadn't noticed the loop in start_subfile. That's great!
>
> > > Either way, this definitely needs a comment. If you'd like to write
> > > up one yourself, great; if not, that's fine; I'll put one in after
> > > your patch goes in.
> >
> > Attached is a new patch that adds comments and removes the superfluous
> > loop. How's that?
>
> If it doesn't cause any regressions, it looks great to me! Thanks very much!
I had regression tested it on i686-linux. I'll check it in in a few
hours time.
Thanks.
next prev parent reply other threads:[~2006-04-21 17:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 11:25 [RFC] Don't loose " Frederic RISS
2006-04-13 17:49 ` Jim Blandy
2006-04-14 7:32 ` [RFC] Don't lose " Frederic RISS
2006-04-14 7:41 ` Jim Blandy
2006-04-14 8:23 ` Frederic RISS
2006-04-14 14:04 ` Daniel Jacobowitz
2006-04-14 14:51 ` Frederic RISS
2006-04-18 12:32 ` Frederic RISS
2006-04-18 13:04 ` Daniel Jacobowitz
2006-04-18 14:00 ` Frederic RISS
2006-04-20 16:27 ` Daniel Jacobowitz
2006-04-21 7:14 ` Frederic RISS
2006-04-21 1:10 ` Jim Blandy
2006-04-21 8:35 ` Frederic RISS
2006-04-21 16:46 ` Jim Blandy
2006-04-21 17:00 ` Frederic RISS [this message]
2006-04-24 12:49 ` Andrew STUBBS
2006-04-14 8:44 ` Eli Zaretskii
2006-04-14 11:44 ` Frederic RISS
2006-04-14 13:08 ` Eli Zaretskii
2006-04-14 13:42 ` Frederic RISS
2006-04-14 14:21 ` Eli Zaretskii
2006-04-14 14:58 ` Daniel Jacobowitz
2006-04-14 15:03 ` Eli Zaretskii
2006-04-14 18:39 ` Frédéric Riss
2006-04-13 19:58 ` [RFC] Don't loose " Jason Molenda
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=1145638813.14807.1094.camel@crx549.cro.st.com \
--to=frederic.riss@st.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.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