From: Tom Tromey <tom@tromey.com>
To: "Tankut Baris Aktemur \(Code Review\)"
<gerrit@gnutoolchain-gerrit.osci.io>
Cc: gdb-patches@sourceware.org, gnutoolchain-gerrit@osci.io,
Tom Tromey <tromey@sourceware.org>
Subject: Re: [review] testsuite, cp: increase the coverage of testing pass-by-ref arguments
Date: Fri, 01 Nov 2019 15:18:00 -0000 [thread overview]
Message-ID: <87tv7n39r8.fsf@tromey.com> (raw)
In-Reply-To: <20191031131928.55CE220AF6@gnutoolchain-gerrit.osci.io> (Tankut Baris Aktemur's message of "Thu, 31 Oct 2019 09:19:28 -0400")
>>>>> "Tankut" == Tankut Baris Aktemur (Code Review) <gerrit@gnutoolchain-gerrit.osci.io> writes:
Tankut> For the latter two, the main reason for failures is that the compiler
Tankut> does not emit the DW_AT_defaulted and DW_AT_deleted attributes. There
Tankut> are more passes with clang because it emits DW_AT_calling_convention,
Tankut> which gcc does not, and the patch I sent favors compiler's hint if it
Tankut> detects a conflict between the DW_AT_calling_convention and the
Tankut> inferred result.
Could you file a GCC bug report for this?
Tom
next prev parent reply other threads:[~2019-11-01 15:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 13:53 Tankut Baris Aktemur (Code Review)
2019-10-28 22:06 ` Tom Tromey (Code Review)
2019-10-31 13:19 ` Tankut Baris Aktemur (Code Review)
2019-11-01 15:18 ` Tom Tromey [this message]
2019-11-08 8:08 ` Aktemur, Tankut Baris
2019-12-09 17:45 ` [review v2] " Tankut Baris Aktemur (Code Review)
2019-12-09 17:56 ` Tankut Baris Aktemur (Code Review)
2019-12-13 21:38 ` Tom Tromey (Code Review)
2019-12-14 9:53 ` [review v3] " Tankut Baris Aktemur (Code Review)
2020-01-13 18:58 ` Luis Machado
2020-01-13 19:38 ` Aktemur, Tankut Baris
[not found] ` <c658e5fb-6d74-04b4-4580-1b07c78a3a79@linaro.org>
2020-01-13 20:21 ` Aktemur, Tankut Baris
[not found] ` <BYAPR11MB3030861F3DA980E1257F02E1C4340@BYAPR11MB3030.namprd11.prod.outlook.com>
[not found] ` <0dd26985-5952-d010-135f-a92aba6f9a05@linaro.org>
2020-01-15 14:41 ` Aktemur, Tankut Baris
2020-01-28 12:30 ` Aktemur, Tankut Baris
2020-01-29 3:18 ` Simon Marchi
2020-01-29 10:54 ` Aktemur, Tankut Baris
2019-12-14 9:56 ` Tankut Baris Aktemur (Code Review)
2019-12-20 7:29 ` Tankut Baris Aktemur (Code Review)
2019-12-20 15:54 ` Tom Tromey (Code Review)
2019-12-20 16:47 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-12-20 16:47 ` Sourceware to Gerrit sync (Code Review)
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=87tv7n39r8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=gerrit@gnutoolchain-gerrit.osci.io \
--cc=gnutoolchain-gerrit@osci.io \
--cc=tromey@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