Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Weimin Pan <weimin.pan@oracle.com>
To: <simon.marchi@polymtl.ca>
Cc: <jose.marchesi@oracle.com>, <qiyaoltc@gmail.com>,
	       <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4] gdb: ADI support
Date: Tue, 25 Jul 2017 22:37:00 -0000	[thread overview]
Message-ID: <16527a85-f249-41d0-8fa2-58db1522a2a9@default> (raw)


----- Original Message -----
> From: simon.marchi@polymtl.ca
> To: weimin.pan@oracle.com
> Cc: qiyaoltc@gmail.com, jose.marchesi@oracle.com, gdb-patches@sourceware.org
> Sent: Tuesday, July 25, 2017 1:18:00 PM GMT -08:00 US/Canada Pacific
> Subject: Re: [PATCH v4] gdb: ADI support
>
> ...
> >
> > Given the fact that we need to backport this new feature to older
> > gdb's, e.g.
> > dev-toolset6, one question is do we need to resort to the linked list
> > solution
> > if the std list implementation is not available in older gdb versions?
> > As of now,
> > we have one diversion already -  uiout->text ("\n") VS ui_out_text
> > (uiout, "\n").
>
> Are you talking about Red Hat devtoolset?  If so, it seems like it
> contains gdb 7.12.  As far as I remember, it was possible to build 7.12
> in both C and C++ mode.  If you don't need to maintain the ability to
> build as C, you should be able to backport a patch using std::list.

Yes, it is. It will be a big plus if we can apply the same fix for both
old and new versions. Will take a look at std::list or forward_list and 
use it over the linked list.

Thanks.


             reply	other threads:[~2017-07-25 22:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 22:37 Weimin Pan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-04 22:46 Weimin Pan
2017-08-01 23:30 Weimin Pan
2017-08-02  7:55 ` Yao Qi
2017-08-02 18:00   ` Wei-min Pan
2017-08-04 11:57     ` Yao Qi
2017-07-25 19:19 Weimin Pan
2017-07-25 20:18 ` Simon Marchi
2017-07-25 21:03   ` Jose E. Marchesi
2017-07-19  0:49 Weimin Pan
2017-07-25 15:16 ` Yao Qi
2017-07-25 15:31   ` Jose E. Marchesi
2017-07-25 16:44     ` Yao Qi
2017-07-26 21:12   ` Wei-min Pan
2017-07-27 11:17     ` Yao Qi
2017-07-27 16:34       ` Wei-min Pan
2017-07-28 10:30         ` Yao Qi
2017-07-28 16:34           ` Wei-min Pan
     [not found]             ` <868tj3ml8s.fsf@gmail.com>
2017-08-01 17:41               ` Wei-min Pan

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=16527a85-f249-41d0-8fa2-58db1522a2a9@default \
    --to=weimin.pan@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=qiyaoltc@gmail.com \
    --cc=simon.marchi@polymtl.ca \
    /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