From: Eric Christopher <echristo@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: binutils@sources.redhat.com, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] Bad DWARF2 line information for MIPS16
Date: Tue, 22 Feb 2005 23:37:00 -0000 [thread overview]
Message-ID: <1109104017.5032.19.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0502221926060.20174@perivale.mips.com>
> the result. Tested for mipsel-linux-gnu, mips64-elf, mips64el-elf,
> mips64-linux-gnu, mips64el-linux-gnu with no regressions and the two
> latters fixed.
>
> 2005-02-22 Maciej W. Rozycki <macro@mips.com>
>
> * gas/mips/mips16-dwarf2.d: Pass -mabi=32. Include relocation
> information.
> * gas/mips/mips16-dwarf2-n32.d: New test to check DWARF2 line
> information for MIPS16 for the n32 ABI.
> * gas/mips/mips.exp. Run the new test.
>
> OK to apply?
OK.
-eric
prev parent reply other threads:[~2005-02-22 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 0:44 Maciej W. Rozycki
2005-02-22 0:57 ` Eric Christopher
2005-02-22 23:30 ` Maciej W. Rozycki
2005-02-22 23:37 ` Eric Christopher [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=1109104017.5032.19.camel@localhost.localdomain \
--to=echristo@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=macro@linux-mips.org \
--cc=macro@mips.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).