From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Cc: qiyaoltc@gmail.com
Subject: Re: [PATCH] Fix length calculation in aarch64_linux_set_debug_regs
Date: Mon, 02 Nov 2015 18:19:00 -0000 [thread overview]
Message-ID: <5637A91F.4020309@redhat.com> (raw)
In-Reply-To: <5637A8BC.3020301@ericsson.com>
On 11/02/2015 06:17 PM, Simon Marchi wrote:
> On 15-11-02 12:57 PM, Pedro Alves wrote:
>> OK. Still not sure whether it's a bug or not. It may still be invalid C++ that
>> happens to be accepted by clang++.
>
> Looking at the standard (well, the latest draft of it), section 18.2, my
> understanding is that it should behave the same way as C. How do you suggest
> we find out?
Maybe ask on gcc-help@.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-11-02 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 14:48 Simon Marchi
2015-11-02 16:00 ` Pedro Alves
2015-11-02 17:09 ` Simon Marchi
2015-11-02 17:57 ` Pedro Alves
2015-11-02 18:17 ` Simon Marchi
2015-11-02 18:19 ` Pedro Alves [this message]
2015-11-02 18:25 ` Andreas Schwab
2015-11-02 16:51 ` Yao Qi
2015-11-19 11:52 ` Yao Qi
2015-11-19 13:32 ` Simon Marchi
2015-11-19 13:51 ` Yao Qi
2015-11-19 15:20 ` Simon Marchi
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=5637A91F.4020309@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).