From: Jakub Jelinek <jakub@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
Jason Merrill <jason@redhat.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] [PR c++/88146] do not crash synthesizing inherited ctor(...)
Date: Wed, 19 Dec 2018 18:52:00 -0000 [thread overview]
Message-ID: <20181219185221.GE23305@tucnak> (raw)
In-Reply-To: <or8t0l8iaw.fsf@lxoliva.fsfla.org>
On Wed, Dec 19, 2018 at 04:47:51PM -0200, Alexandre Oliva wrote:
> On Dec 19, 2018, Christophe Lyon <christophe.lyon@linaro.org> wrote:
>
> > The new test inh-ctor32.C fails on arm:
> > FAIL: g++.dg/cpp0x/inh-ctor32.C -std=c++14 (test for warnings, line 208)
> > FAIL: g++.dg/cpp0x/inh-ctor32.C -std=c++17 (test for warnings, line 208)
>
> Thanks, sorry about the breakage, I'm looking into it.
>
> I'm very surprised and puzzled that the messages actually differ across
> targets, but I managed to get the same messages you got, with a cross
> compiler targeting arm-unknown-linux-gnueabi, that are slightly
> different from those I get with a native x86_64-linux-gnu compiler built
> out of the same sources.
ARM returns this from ctors, compared to most other targets that return
void. Maybe something related to that?
Jakub
next prev parent reply other threads:[~2018-12-19 18:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 0:23 Alexandre Oliva
2018-12-14 20:14 ` Alexandre Oliva
2018-12-14 20:42 ` Jason Merrill
2018-12-14 21:41 ` Jason Merrill
2018-12-14 22:34 ` Alexandre Oliva
2018-12-14 22:44 ` Jason Merrill
2018-12-14 23:05 ` Alexandre Oliva
2018-12-15 22:11 ` Jason Merrill
2018-12-19 14:36 ` Christophe Lyon
2018-12-19 18:49 ` Alexandre Oliva
2018-12-19 18:52 ` Jakub Jelinek [this message]
2018-12-20 0:04 ` Alexandre Oliva
2018-12-20 16:00 ` Christophe Lyon
2018-12-20 16:18 ` Jason Merrill
2018-12-28 22:53 ` Alexandre Oliva
2018-12-29 6:40 ` Alexandre Oliva
2018-12-29 13:33 ` Jakub Jelinek
2019-01-04 18:55 ` Jason Merrill
2019-01-17 4:12 ` Alexandre Oliva
2018-12-29 10:28 ` Alexandre Oliva
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=20181219185221.GE23305@tucnak \
--to=jakub@redhat.com \
--cc=aoliva@redhat.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).