Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Luis Machado <luis.machado@linaro.org>,
	"tromey@sourceware.org"	<tromey@sourceware.org>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>
Subject: RE: [review v3] testsuite, cp: increase the coverage of testing pass-by-ref arguments
Date: Wed, 15 Jan 2020 14:41:00 -0000	[thread overview]
Message-ID: <BYAPR11MB30307D89EB09CB0AEC9E5577C4370@BYAPR11MB3030.namprd11.prod.outlook.com> (raw)
In-Reply-To: <0dd26985-5952-d010-135f-a92aba6f9a05@linaro.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1797 bytes --]

On Tuesday, January 14, 2020 2:13 PM, Luis Machado wrote:
> 
> On 1/14/20 9:52 AM, Aktemur, Tankut Baris wrote:
> >
> > I've investigated GCC and Clang for this.  GCC started emitting DW_AT_deleted and
> > DW_AT_defaulted with version 7.  Clang does not emit these attributes; however, it
> > has been emitting DW_AT_calling_convention starting with version 7.  This
> > attribute helps the debugger make the right decision in some cases.
> >
> > Based on this, I think the test cases have to be filtered in a somewhat
> > fine-granular manner.  Therefore I thought I could save you from the burden of
> > having to go through the code-generating test definition.  Below is a patch proposal.
> >
> > -Baris
> 
> Thanks! I've checked this on my box with an older GCC and i see the
> XFAIL's now. So it looks good to me.
> 
> Small nit below...
> 

Thank you.  I'll fix that and wait for an official approval.

-Baris

> > +# GCC version <= 6 and Clang do not emit DW_AT_defaulted and DW_AT_deleted
> > +set is_gcc_6_or_older [test_compiler_info {gcc-[0-6]-*}]
> > +set is_clang [test_compiler_info {clang-*}]
> > +
> >   set bp_location [gdb_get_line_number "stop here"]
> >   gdb_breakpoint $bp_location
> >   gdb_continue_to_breakpoint "end of main" ".*return .*;"
> 
> It seems to be a mixed bag, but i see more examples of having a period
> after the sentence than not having it. Multiple cases of this on the patch.
> 
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
\x16º&Öéj×!zÊÞ¶êç×­õÓ©b²Ö«r\x18\x1dn–­r\x17¬

  parent reply	other threads:[~2020-01-15 14:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 13:53 [review] " 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
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 [this message]
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=BYAPR11MB30307D89EB09CB0AEC9E5577C4370@BYAPR11MB3030.namprd11.prod.outlook.com \
    --to=tankut.baris.aktemur@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --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