Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pierre-Marie de Rodat <derodat@adacore.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	 GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Do not consider reference types as dynamic
Date: Fri, 17 Apr 2015 10:47:00 -0000	[thread overview]
Message-ID: <86k2xbrpzs.fsf@gmail.com> (raw)
In-Reply-To: <551E5309.7090509@adacore.com> (Pierre-Marie de Rodat's message	of "Fri, 03 Apr 2015 10:44:57 +0200")

Pierre-Marie de Rodat <derodat@adacore.com> writes:

> I've tried to do this and this still triggers no regression on
> x86_64-linux. It's not surprising actually, since
> resolve_dynamic_type_internal does nothing on a type when
> is_dynamic_type_internal returns false for it.

Hi, Pierre,
This patch causes a regression in gdb.cp/vla-cxx.exp unfortunately,

 print vlaref^M
 $2 = (int (&)[variable length]) @0x3fffffffe900: {5, 7, 9}^M
 (gdb) FAIL: gdb.cp/vla-cxx.exp: print vlaref

which is shown by buildbot
https://sourceware.org/ml/gdb-testers/2015-q2/msg00360.html

I am not familiar with gdb type and dynamic type, so can't give anything
useful on how to fix this regression.  Any thoughts?

-- 
Yao (齐尧)


  parent reply	other threads:[~2015-04-17 10:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 11:57 Pierre-Marie de Rodat
2015-03-23 13:36 ` Joel Brobecker
2015-04-01  8:52   ` Pierre-Marie de Rodat
2015-04-03  8:45     ` Pierre-Marie de Rodat
2015-04-03 12:47       ` Joel Brobecker
2015-04-03 13:02         ` Pierre-Marie de Rodat
2015-04-03 13:12           ` Joel Brobecker
2015-04-03 13:25             ` Pierre-Marie de Rodat
2015-04-17 10:47       ` Yao Qi [this message]
2015-04-17 11:20         ` Pierre-Marie de Rodat
2015-04-17 15:07           ` Pierre-Marie de Rodat
2015-04-17 15:29             ` Joel Brobecker
2015-04-20 14:27               ` Pierre-Marie de Rodat
2015-04-24 14:22                 ` Pierre-Marie de Rodat

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=86k2xbrpzs.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=derodat@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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