From: Petr Sorfa <petrs@caldera.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Waiting for review since April
Date: Mon, 17 Jun 2002 09:23:00 -0000 [thread overview]
Message-ID: <3D0E0FC9.A6A1D742@caldera.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206171049240.5614-100000@dberlin.org>
Hi Daniel,
I had a brief look and it looks ok.
Petr
> Could someone take a look at
> http://sources.redhat.com/ml/gdb-patches/2002-04/msg00432.html, please?
>
> Feel free to evaluate the loc_computed/loc_computed_arg portion separate
> from the dwarf2 portion, i can split the patch if necessary, but i'm not
> going to bother if it's not going to be looked at.
>
> The loc_computed/loc_computed_arg is an implementation of Jim's spec that
> he posted, so any complaints on the idea itself/the structure in symtab.h
> (which was cut and pasted from his email), should probably go to him.
>
> As the patch mentions, it was tested on multiple platforms.
> --Dan
next prev parent reply other threads:[~2002-06-17 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 7:54 Daniel Berlin
2002-06-17 9:23 ` Petr Sorfa [this message]
2002-06-18 11:44 ` Daniel Berlin
2002-06-18 11:49 ` Petr Sorfa
2002-06-18 12:43 ` Elena Zannoni
2002-07-02 8:34 ` Daniel Berlin
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=3D0E0FC9.A6A1D742@caldera.com \
--to=petrs@caldera.com \
--cc=dberlin@dberlin.org \
--cc=gdb-patches@sources.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