From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Rewrite valid-expr.h's internals in terms of the detection idiom (C++17/N4502)
Date: Tue, 29 Sep 2020 07:04:14 -0600 [thread overview]
Message-ID: <87a6x8hgz5.fsf@tromey.com> (raw)
In-Reply-To: <87eemlhdti.fsf@tromey.com> (Tom Tromey's message of "Mon, 28 Sep 2020 14:00:09 -0600")
>>> I'm not sure if it was exactly this patch, but after I merged this code
>>> to our internal tree, we started having build problems on a machine that
>>> uses GCC 6.4. I've appended the error message.
>>> I'm not sure it is worth doing anything about this, but I thought it
>>> would be worth noting in case anybody else winds up in this situation.
>>> Tom
Luis> It was reported before on this thread a week or so ago. Unless GCC 6.4
Luis> isn't supported any longer, I think it should be fixed.
Tom> Ok, thanks. I will find out tonight.
Oops, I really misunderstood your note, and re-reading it now I can't
really understand why. I thought you were saying it was fixed, but
really you were saying it is still there and should be fixed if we want
to support GCC 6.4.
I am not sure if we should try to fix it or not. Locally I plan to
disable unit tests on this particular machine. It is the only one using
6.4.
Tom
next prev parent reply other threads:[~2020-09-29 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 14:45 [PATCH 0/3] Rewrite enum_flags, add unit tests, fix problems Pedro Alves
2020-08-21 14:45 ` [PATCH 1/3] Rewrite valid-expr.h's internals in terms of the detection idiom (C++17/N4502) Pedro Alves
2020-09-28 18:59 ` Tom Tromey
2020-09-28 19:58 ` Luis Machado via Gdb-patches
2020-09-28 20:00 ` Tom Tromey
2020-09-29 13:04 ` Tom Tromey [this message]
2020-09-29 19:24 ` Pedro Alves
2020-09-29 22:50 ` [pushed] Tweak gdbsupport/valid-expr.h for GCC 6, fix build (Re: [PATCH 1/3] Rewrite valid-expr.h's internals in terms of the detection idiom (C++17/N4502)) Pedro Alves
2020-08-21 14:45 ` [PATCH 2/3] Use type_instance_flags more throughout Pedro Alves
2020-08-25 11:36 ` Luis Machado
2020-09-14 11:56 ` Pedro Alves
2020-08-26 10:06 ` Andrew Burgess
2020-09-14 12:54 ` Pedro Alves
2020-08-26 15:21 ` Andrew Burgess
2020-09-14 13:53 ` Pedro Alves
2020-09-11 20:21 ` Tom Tromey
2020-09-14 19:26 ` Pedro Alves
2020-08-21 14:45 ` [PATCH 3/3] Rewrite enum_flags, add unit tests, fix problems Pedro Alves
2020-08-21 15:51 ` [PATCH 0/3] " Andrew Burgess
2020-09-11 20:26 ` Tom Tromey
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=87a6x8hgz5.fsf@tromey.com \
--to=tromey@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