public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: binutils@sourceware.org, Victor Leschuk <vleschuk@accesssoftek.com>
Subject: Re: [PATCH 1/6] DWARF attrs: add delimiter
Date: Fri, 17 Feb 2017 08:37:00 -0000	[thread overview]
Message-ID: <5841def0-93f9-2d93-ad97-ec63b01e367c@redhat.com> (raw)
In-Reply-To: <20170216201329.GA22230@host1.jankratochvil.net>

Hi Jan,

> before coding it - is it OK do use x86_64 specific .s (and output .d) files
> where .s is built with?
> 	-gdwarf-5 -S -dA
> 
> I understand an arch-independent .s file would be better but that would need
> a lot of hand coding IMO.

Yes and no ... :-)

What I suggest is that you use "-gdwarf-5 -S -dA" to create the .s file.  Then
strip any x86_64 instructions from it, (replacing them with .dc.b directives or
something similar if you need to make sure that the region concerned has some
content), and then use this reduced, and hopefully target neutral, assembler 
source file as the input for the new test(s).

IE we really do want a test that will work across all, or at least most, architectures
unless you need to test architecture specific parts of the DWARF-5 standard.  (Are 
there any architecture specific parts of the new standard ?)  I do not mind if you
have to add XFAILs for a few architectures, as I know that some of them can be a bit
funny when it comes to generating DWARF information.  But ideally we should be sure
that the encoding and decoding works for as many architectures as possible.

Cheers
  Nick

PS.  If you a potential test case, but you do not want to spin up 200+ toolchains to
test all of the potential targets then feel free to send it to me.  I already have
the toolchains set up and I can quickly run the new test past them all...

  reply	other threads:[~2017-02-17  8:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 22:58 Jan Kratochvil
2017-02-15 22:58 ` [PATCH 6/6] DWARF-5: DW_FORM_data16 Jan Kratochvil
2017-02-22 11:51   ` Nick Clifton
2017-02-23 22:13     ` [commit] " Jan Kratochvil
2017-02-15 22:58 ` [PATCH 5/6] DWARF-5: Macros Jan Kratochvil
2017-02-22 11:50   ` Nick Clifton
2017-02-23 22:13     ` [commit] " Jan Kratochvil
2017-02-15 22:58 ` [PATCH 3/6] DWARF-5 basic functionality Jan Kratochvil
2017-02-22 11:36   ` Nick Clifton
2017-02-22 18:42     ` Jan Kratochvil
2017-02-22 11:47   ` Nick Clifton
2017-02-22 19:13     ` [patch] dwarf.c: Use more dwarf_vma [Re: [PATCH 3/6] DWARF-5 basic functionality] Jan Kratochvil
2017-02-23 16:34       ` Nick Clifton
2017-02-23 16:35       ` Nick Clifton
2017-02-23 20:38         ` [commit] " Jan Kratochvil
2017-02-23 22:12     ` [commit] [PATCH 3/6] DWARF-5 basic functionality Jan Kratochvil
2017-02-27 21:58       ` Maciej W. Rozycki
2017-02-27 22:24         ` [obv] DWARF-5: Fix compilation with GCC 4.4.7 [Re: [commit] [PATCH 3/6] DWARF-5 basic functionality] Jan Kratochvil
2017-02-15 22:58 ` [PATCH 4/6] DWARF-5: call sites Jan Kratochvil
2017-02-22 11:49   ` Nick Clifton
2017-02-23 22:12     ` [commit] " Jan Kratochvil
2017-02-15 22:58 ` [PATCH 2/6] Display user op byte Jan Kratochvil
2017-02-22 11:30   ` Nick Clifton
2017-02-22 19:24     ` [commit] " Jan Kratochvil
2017-02-16 10:59 ` [PATCH 1/6] DWARF attrs: add delimiter Nick Clifton
2017-02-16 20:13   ` Jan Kratochvil
2017-02-17  8:37     ` Nick Clifton [this message]
2017-02-18 19:47       ` [patch] DWARF-5: testcase [Re: [PATCH 1/6] DWARF attrs: add delimiter] Jan Kratochvil
2017-02-21  9:44         ` Nick Clifton
2017-02-23 22:17           ` [commit] [patch] DWARF-5: testcase Jan Kratochvil
2017-02-22 11:48 ` [PATCH 1/6] DWARF attrs: add delimiter Nick Clifton
2017-02-23 22:08   ` [commit] " 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=5841def0-93f9-2d93-ad97-ec63b01e367c@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=vleschuk@accesssoftek.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).