public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/18139] New: gdb.linespec/break-asm-file.exp needs some tweak for non-x86 target
Date: Wed, 18 Mar 2015 11:21:00 -0000 [thread overview]
Message-ID: <bug-18139-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18139
Bug ID: 18139
Summary: gdb.linespec/break-asm-file.exp needs some tweak for
non-x86 target
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: qiyao at gcc dot gnu.org
the test case has an assumption that ".int 0" is a valid instruction,
func2:
.Lbegin_func2:
.int 0
.int 0
.Lend_func2:
.size func2, .-func2
.globl _func
however, it is not true on many other targets. This test fails on arm,
aarch64, ppc and s390x.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-03-18 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 11:21 qiyao at gcc dot gnu.org [this message]
2015-03-18 16:50 ` [Bug testsuite/18139] " qiyao at gcc dot gnu.org
2015-03-26 8:33 ` cvs-commit at gcc dot gnu.org
2015-03-26 13:04 ` qiyao 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-18139-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).