Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: thomas@codesourcery.com
Cc: binutils@sourceware.org, aoliva@redhat.com,
	gdb-patches@sourceware.org,        kevinb@redhat.com
Subject: Re: [SH] .8byte directive (for DWARF data)
Date: Wed, 21 Mar 2012 03:11:00 -0000	[thread overview]
Message-ID: <20120321.121127.243831052.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <87vclzgvfx.fsf@schwinge.name>

Thomas Schwinge <thomas@codesourcery.com> wrote:
> On SH, GDB's gdb.dwarf2/dw2-intermix.exp currently fails as follows:
> 
>     Running [GDB]/testsuite/gdb.dwarf2/dw2-intermix.exp ...
>     gdb compile failed, [GDB]/testsuite/gdb.dwarf2/dw2-intermix.S: Assembler messages:
>     [GDB]/testsuite/gdb.dwarf2/dw2-intermix.S:139: Error: unsupported BFD relocation size 8
>     [GDB]/testsuite/gdb.dwarf2/dw2-intermix.S:142: Error: unsupported BFD relocation size 8
> 
> gdb.dwarf2/dw2-intermix.S:
> 
>     [...]
>         18	/* Test a minimal file containing intermixed 32-bit and 64-bit DWARF
>         19	   formats.  This is not allowed by the (draft) DWARF-3 standard, but
>         20	   GDB should handle it gracefully nevertheless.  */
>     [...]
>        135	/* Line table */
>        136		.section .debug_line
>        137	.Lline1_begin:
>        138		.4byte		0xffffffff
>        139		.8byte		.Lline1_end - .Lline1_start	/* Initial length */
>        140	.Lline1_start:
>        141		.2byte		2			/* Version */
>        142		.8byte		.Lline1_lines - .Lline1_hdr	/* header_length */
>        143	.Lline1_hdr:
>        144		.byte		1			/* Minimum insn length */
>     [...]
> 
> Here is a patch for the assembler, OK to commit?

OK.  Thanks for the patch!

Regards,
	kaz


  reply	other threads:[~2012-03-21  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 15:11 Thomas Schwinge
2012-03-21  3:11 ` Kaz Kojima [this message]
2012-03-21  9:01   ` Thomas Schwinge

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=20120321.121127.243831052.kkojima@rr.iij4u.or.jp \
    --to=kkojima@rr.iij4u.or.jp \
    --cc=aoliva@redhat.com \
    --cc=binutils@sourceware.org \
    --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