From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gdb-patches@sourceware.org, Kevin Buettner <kevinb@redhat.com>
Subject: Re: [SH] gdb.dwarf2 tests: use .byte4 instead of .long
Date: Wed, 14 Mar 2012 19:35:00 -0000 [thread overview]
Message-ID: <20120314193509.GA30809@host2.jankratochvil.net> (raw)
In-Reply-To: <87d38gl7r2.fsf@schwinge.name>
On Tue, 13 Mar 2012 18:40:17 +0100, Thomas Schwinge wrote:
> gdb.dwarf2/dw2-double-set-die-type.S: Assembler messages:
> gdb.dwarf2/dw2-double-set-die-type.S:45: Error: misaligned data
> gdb.dwarf2/dw2-double-set-die-type.S:53: Error: misaligned data
> [...]
That repeatedly happens (at least for s390x (ppc?) I also test), going to post
some ARI check for it.
> OK to commit?
>
> gdb/testsuite/
>
> * gdb.dwarf2/dw2-ada-ffffffff.S: Use .4byte instead of .long for
> describing DWARF data structures.
> * gdb.dwarf2/dw2-bad-parameter-type.S: Likewise.
> * gdb.dwarf2/dw2-double-set-die-type.S: Likewise.
> * gdb.dwarf2/dw2-empty-pc-range.S: Likewise.
> * gdb.dwarf2/dw2-entry-value.S: Likewise.
> * gdb.dwarf2/dw2-modula2-self-type.S: Likewise.
> * gdb.dwarf2/dw2-param-error.S: Likewise.
> * gdb.dwarf2/dw2-skip-prologue.S: Likewise.
> * gdb.dwarf2/dw2-stack-boundary.S: Likewise.
> * gdb.dwarf2/dw4-sig-type-unused.S: Likewise.
> * gdb.dwarf2/implptr-optimized-out.S: Likewise.
> * gdb.dwarf2/member-ptr-forwardref.S: Likewise.
> * gdb.dwarf2/pr11465.S: Likewise.
Yes, please check it in.
Thanks,
Jan
next prev parent reply other threads:[~2012-03-14 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 17:40 Thomas Schwinge
2012-03-14 19:35 ` Jan Kratochvil [this message]
2012-03-14 20:17 ` Pedro Alves
2012-03-14 20:26 ` Jan Kratochvil
2012-03-14 20:33 ` Pedro Alves
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=20120314193509.GA30809@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=thomas@codesourcery.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