From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] xtensa: Avoid designated inits, for C++ compliance
Date: Fri, 26 Aug 2016 10:10:00 -0000 [thread overview]
Message-ID: <20160826100946.GA4556@host1.jankratochvil.net> (raw)
In-Reply-To: <62e78020-2079-2c29-08c9-f930c43c37ea@redhat.com>
On Fri, 26 Aug 2016 11:39:27 +0200, Pedro Alves wrote:
> We're still doing many 7.12 backports, so I was waiting for that
> to stabilize before proposing to drop C support.
Ah, OK.
> > https://en.wikipedia.org/wiki/One_Definition_Rule
>
> Right, we're not LTO-ready yet. Note -Wodr (w/ -flto) helps find these.
In this case there would be gdbarch_tdep() ctor handy but that is also not
applicable without ODR. OK, I see I missed GDB still does not require C++.
Jan
prev parent reply other threads:[~2016-08-26 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 11:56 Andreas Arnez
2016-08-25 16:33 ` Pedro Alves
2016-08-25 17:17 ` Andreas Arnez
2016-08-26 9:42 ` Pedro Alves
2016-08-26 11:39 ` Andreas Arnez
2016-08-26 9:02 ` Jan Kratochvil
2016-08-26 9:07 ` Eli Zaretskii
2016-08-26 9:39 ` Pedro Alves
2016-08-26 10:10 ` Jan Kratochvil [this message]
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=20160826100946.GA4556@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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