From: Luis Machado <luis.machado@linaro.org>
To: Gary Benson <gbenson@redhat.com>, Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Enable gdb.cp/ambiguous.exp with GCC and clang
Date: Wed, 26 Aug 2020 14:13:00 -0300 [thread overview]
Message-ID: <a5062f9e-3d3e-5aa9-e253-d90aade34f24@linaro.org> (raw)
In-Reply-To: <20200825142146.GA14101@blade.nx>
Hi,
On 8/25/20 11:21 AM, Gary Benson via Gdb-patches wrote:
> Pedro Alves wrote:
>> On 8/17/20 2:24 PM, Gary Benson wrote:
>>> Pedro Alves wrote:
>>>> On 7/27/20 2:09 PM, Gary Benson via Gdb-patches wrote:
>>>>> + unsupported "compiler does not support -Wno-inaccessible-base"
>>>>
>>>> How about instead of bailing out, use "-Wno-inaccessible-base"
>>>> with GCC >= 10, and use "-w" with older GCCs?
>>>
>>> Sure. How about this?
>>
>> OK.
>
> Thanks, I pushed it.
I get the following, under Ubuntu 18.04 (GCC 7.x) with this commit...
FAIL: gdb.cp/ambiguous.exp: print x.x
FAIL: gdb.cp/ambiguous.exp: print n.x
FAIL: gdb.cp/ambiguous.exp: print j.x
FAIL: gdb.cp/ambiguous.exp: print jva1.x
FAIL: gdb.cp/ambiguous.exp: print jva2.x
FAIL: gdb.cp/ambiguous.exp: print (A1)j
FAIL: gdb.cp/ambiguous.exp: print (A1)jva1
Is the test really supposed to run with older GCC's?
next prev parent reply other threads:[~2020-08-26 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:09 [PATCH] Enable gdb.cp/ambiguous.exp with GCC >= 10.1 " Gary Benson
2020-08-07 15:27 ` Pedro Alves
2020-08-17 13:24 ` [PATCH v2] Enable gdb.cp/ambiguous.exp with GCC " Gary Benson
2020-08-17 14:00 ` Pedro Alves
2020-08-17 14:57 ` Gary Benson
2020-08-25 14:21 ` Gary Benson
2020-08-26 17:13 ` Luis Machado [this message]
2020-08-27 10:39 ` Gary Benson
2020-08-27 11:20 ` Pedro Alves
2020-08-27 11:25 ` Luis Machado
2020-08-27 15:07 ` Gary Benson
2020-08-27 15:47 ` Pedro Alves
2020-08-27 16:18 ` Gary Benson
2020-08-27 18:04 ` Pedro Alves
2020-09-11 13:59 ` Tom de Vries
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=a5062f9e-3d3e-5aa9-e253-d90aade34f24@linaro.org \
--to=luis.machado@linaro.org \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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