public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/18933] New: gdb.arch/aarch64-atomic-inst.c needs to fix for ILP32
Date: Mon, 07 Sep 2015 17:14:00 -0000	[thread overview]
Message-ID: <bug-18933-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18933
           Summary: gdb.arch/aarch64-atomic-inst.c needs to fix for ILP32
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

This testcase uses long which is different between LP64 and ILP32 ABIS.
  unsigned long tmp, cond;
  unsigned long dword = 0;

  /* Test that we can step over ldxr/stxr. This sequence should step from
     ldxr to the following __asm __volatile.  */
  __asm __volatile ("1:     ldxr    %0,%2\n"                             \
                    "       cmp     %0,#1\n"                             \
                    "       b.eq    out\n"                               \
                    "       add     %0,%0,1\n"                           \
                    "       stxr    %w1,%0,%2\n"                         \
                    "       cbnz    %w1,1b"                              \
                    : "=&r" (tmp), "=&r" (cond), "+Q" (dword)            \
                    : : "memory");

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


             reply	other threads:[~2015-09-07 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 17:14 pinskia at gcc dot gnu.org [this message]
2015-09-07 17:14 ` [Bug testsuite/18933] " pinskia 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-18933-4717@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).