Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Pedro Alves <palves@redhat.com>,
	binutils@sourceware.org,        gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb passes and returns incorrect values when dealing with small array on Sparc
Date: Wed, 29 Mar 2017 16:38:00 -0000	[thread overview]
Message-ID: <58DBE2F2.4080504@oracle.com> (raw)
In-Reply-To: <5a3397ae-e986-8a36-13ba-ed2cfeb68a12@redhat.com>

On 03/29/2017 02:56 AM, Pedro Alves wrote:
> Hi Vladimir,
>
> gdb development happens on a separate list - gdb-patches@.  Please resend
> the patch there.  TIA!

  Done.
>
> A question I'll have is whether this had any observable effect in testsuite
> results, other than "no regressions".  I.e., whether there were progressions,
> or whether we're missing testsuite coverage.

6 tests ( from gdb/testsuite/gdb.base/gnu_vector.exp) failed on 
sparc64-Linux  and on sparc-Solaris in 32- and 64-bit mode.
Now all these tests passed.

gdb/testsuite/gdb.base/gnu_vector.exp has 117 different cases for small 
(and not small) arrays and structures.
I think we don't need an additional test in gdb/testsuite.

-Vladimir


>
> On 03/28/2017 06:21 PM, vladimir.mezentsev@oracle.com wrote:
>> From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>>
>> 	gdb has a special type (TYPE_CODE_ARRAY) to support the gcc extension
>> 	(https://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html).
>> 	TYPE_CODE_ARRAY is handled incorrectly for both (32- and 64-bit) modes on Sparc machines.
>>
>> 	Tested on sparc64-linux-gnu and sparc-solaris (32- and 64-bit mode).
>> 	No regressions.
>>
>> 	2017-03-27 Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
>>
>> 	* gdb/sparc-tdep.c (sparc_structure_return_p): New function.
> Also, please drop "gdb/" here.  Filename entries in ChangeLogs
> are relative to the ChangeLog file path.
>
> Thanks,
> Pedro Alves
>


       reply	other threads:[~2017-03-29 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1490721669-12560-1-git-send-email-vladimir.mezentsev@oracle.com>
     [not found] ` <5a3397ae-e986-8a36-13ba-ed2cfeb68a12@redhat.com>
2017-03-29 16:38   ` Vladimir Mezentsev [this message]
2017-04-18 14:54     ` Pedro Alves
2017-05-16 16:16 vladimir.mezentsev
2017-05-19  9:44 ` Jose E. Marchesi
2017-05-19  9:57   ` Pedro Alves
2017-05-19 10:19     ` Jose E. Marchesi
  -- strict thread matches above, loose matches on Subject: below --
2017-03-29 16:21 vladimir.mezentsev
2017-04-18 14:54 ` Pedro Alves
2017-04-18 21:28   ` Jose E. Marchesi
2017-04-18 22:20     ` Pedro Alves
2017-04-19  9:01       ` Jose E. Marchesi

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=58DBE2F2.4080504@oracle.com \
    --to=vladimir.mezentsev@oracle.com \
    --cc=binutils@sourceware.org \
    --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