From: Thomas Schwinge <thomas@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [testuite patch] Fix cross-arch .S testsuite files compatibility
Date: Thu, 15 Mar 2012 08:57:00 -0000 [thread overview]
Message-ID: <87aa3ikzrs.fsf@schwinge.name> (raw)
In-Reply-To: <20120314201849.GB1412@host2.jankratochvil.net>
[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]
Hi!
On Wed, 14 Mar 2012 21:20:20 +0100, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> on top of:
> [SH] gdb.dwarf2 tests: use .byte4 instead of .long
> http://sourceware.org/ml/gdb-patches/2012-03/msg00447.html
>
> some parts of this patch may not be required (such as
> gdb.arch/amd64-entry-value.s does not need fixes for non-amd64 asm compilers)
> but it has been made to make gdb_ari.sh quiet with its patch posting along).
>
> No regressions on {x86_64,x86_64-m32,i686}-fedora17-linux-gnu.
> gdb/testsuite/
> 2012-03-14 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix build compatibility with non-x86* archs.
> * gdb.arch/amd64-entry-value.s: Replace # by /**/, .long by .4byte,
> .value by .2byte, drop #APP and #NO_APP.
> * [...]
In my patch I had explicitly taken care to replace .long with .4byte only
in .debug_* sections (and only in files that are not x86-specific, as it
doesn't matter for those). You're now proposing such changes, too:
--- a/gdb/testsuite/gdb.dwarf2/dw2-modula2-self-type.S
+++ b/gdb/testsuite/gdb.dwarf2/dw2-modula2-self-type.S
@@ -22,7 +22,7 @@
But "v" has been removed afterwards. */
.data
-v: .long 0
+v: .4byte 0
Or:
--- a/gdb/testsuite/gdb.dwarf2/typeddwarf-amd64.S
+++ b/gdb/testsuite/gdb.dwarf2/typeddwarf-amd64.S
@@ -175,24 +175,24 @@ _start:
.section .rodata.cst8,"aM",@progbits,8
.align 8
.LC0:
- .long 0
- .long 1074266112
+ .4byte 0
+ .4byte 1074266112
I just wanted to check whether we can be sure that .4byte always conveys
the same meaning as .long did in such cases? For example, on SH you
wouldn't get the alignment mismatch error (that prompted my original
patch) -- but that probably doesn't matter for the GDB testsuite, as we
would always have conforming assembler files (where no assembler errors
are expected; as opposed to the gas testsuite). Can there be other
semantic differences between the two?
(And no, I don't think you could reasonably encode ``don't allow .long --
but only in .debug_* sections'' in the ARI system...) :-)
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2012-03-15 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 20:27 Jan Kratochvil
2012-03-15 8:57 ` Thomas Schwinge [this message]
2012-03-15 9:06 ` Jan Kratochvil
2012-03-15 9:32 ` Thomas Schwinge
2012-03-16 8:52 ` Jan Kratochvil
2012-03-21 11:37 ` Thomas Schwinge
2012-03-19 14:04 ` Jan Kratochvil
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=87aa3ikzrs.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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