From: Pedro Alves <pedro@palves.net>
To: Gary Benson <gbenson@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Enable gdb.cp/ambiguous.exp with GCC and clang
Date: Mon, 17 Aug 2020 15:00:00 +0100 [thread overview]
Message-ID: <4b7a4f2e-9e77-495a-759b-187aebb342aa@palves.net> (raw)
In-Reply-To: <1597670664-14171-1-git-send-email-gbenson@redhat.com>
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:
>>> Furthermore, gdb.cp/ambiguous.exp has been disabled when using GCC
>>> since 1998.
>>
>> Curious you reference the year, do you know it because you found the
>> commit that disabled it?
>
> Yes :)
What it was, then? Does it say anything about why the testcase
was disabled?
>
>>> -if { [test_compiler_info gcc-*] } then { continue }
>>> +# GCCs prior to 10.1 do not support -Wno-inaccessible-base.
>>> +if { [test_compiler_info {gcc-[0-9]-*}]
>>> + || [test_compiler_info {gcc-10-0-*}] } {
>>
>> Given the first release of GCC 10 is 10.1...
>
> Ah, I didn't know that.
>
>> ...do we really need the second check?
>
> No :) I've removed it.
>
>>> + 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,
Pedro Alves
next prev parent reply other threads:[~2020-08-17 14:00 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 [this message]
2020-08-17 14:57 ` Gary Benson
2020-08-25 14:21 ` Gary Benson
2020-08-26 17:13 ` Luis Machado
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=4b7a4f2e-9e77-495a-759b-187aebb342aa@palves.net \
--to=pedro@palves.net \
--cc=gbenson@redhat.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