From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
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 20:33:00 -0000 [thread overview]
Message-ID: <4F610086.4070006@redhat.com> (raw)
In-Reply-To: <20120314202554.GA2026@host2.jankratochvil.net>
On 03/14/2012 08:25 PM, Jan Kratochvil wrote:
> On Wed, 14 Mar 2012 21:17:07 +0100, Pedro Alves wrote:
>> Is this due to the test having been originally written by adjusting gcc output?
>
> No, amd64 gcc just produces .long and .value.
/me confused :-)
>> Maybe gcc could be changed to emit .byte4 instead?
>
> I was looking at it once already but there are some concerns with
> compatibility with various non-GNU assemblers I was unaware of at all.
> As the assembler directives are chosen according to the target arch GCC can
> always adjust it accordingly. Multi-arch GDB testfiles cannot.
>
> It is true this .4byte directive probably breaks compatibility with some
> non-GNU assemblers but I believe easy cross-arch compatibility is of a more
> concern to GDB than such non-GNU assemblers compatibility. Or is it?
IMO, yes. There's always putting the .byte4/.something behind
preprocessor macros if somebody cares.
--
Pedro Alves
prev parent reply other threads:[~2012-03-14 20:33 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
2012-03-14 20:17 ` Pedro Alves
2012-03-14 20:26 ` Jan Kratochvil
2012-03-14 20:33 ` Pedro Alves [this message]
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=4F610086.4070006@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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