public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/27007] [-m32] FAIL: gdb.cp/many-args.exp: check passing many structures
Date: Thu, 03 Dec 2020 12:21:32 +0000	[thread overview]
Message-ID: <bug-27007-4717-bu2ygI0eJg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27007-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27007

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Minimal version:
...
$ cat gdb/testsuite/gdb.cp/many-args.cc      
typedef int v4si __attribute__ ((vector_size (16)));

struct ss
{
  static v4si static_field;
  unsigned char aa;
};

bool
check_val (ss v1, ss v2)
{
  return (v1.aa == 'a' && v2.aa == 'a');
}

int
main (void)
{
  ss ref_val = { 'a' };
  bool flag = check_val (ref_val, ref_val);
  return (flag ? 0 : 1);        /* break-here */
}
$ gcc -g gdb/testsuite/gdb.cp/many-args.cc -m32
$ ./a.out; echo $?
0
$ gdb -batch a.out -ex start -ex n -ex n -ex "p check_val (ref_val, ref_val)"
Temporary breakpoint 1 at 0x804842d: file gdb/testsuite/gdb.cp/many-args.cc,
line 18.

Temporary breakpoint 1, main () at gdb/testsuite/gdb.cp/many-args.cc:18
18        ss ref_val = { 'a' };
19        bool flag = check_val (ref_val, ref_val);
20        return (flag ? 0 : 1);        /* break-here */
$1 = false
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2020-12-03 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 12:21 [Bug tdep/27007] New: " vries at gcc dot gnu.org
2020-12-03 12:21 ` vries at gcc dot gnu.org [this message]
2020-12-03 12:40 ` [Bug tdep/27007] " vries at gcc dot gnu.org
2020-12-03 12:44 ` vries at gcc dot gnu.org
2020-12-04 12:37 ` cvs-commit at gcc dot gnu.org
2020-12-04 12:39 ` vries at gcc dot gnu.org

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=bug-27007-4717-bu2ygI0eJg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).