From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Steve Ellcey " <sellcey@mips.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, mips, stabs] Do any MIPS targets use stabs?
Date: Mon, 07 Jan 2013 20:30:00 -0000 [thread overview]
Message-ID: <87ip784tyl.fsf@talisman.default> (raw)
In-Reply-To: <99d6779b-5dee-4fac-bc73-26055eaa0857@EXCHHUB01.MIPS.com> (Steve Ellcey's message of "Mon, 7 Jan 2013 10:27:26 -0800")
"Steve Ellcey " <sellcey@mips.com> writes:
> While testing all the variations of my mips-mti-elf target I found that
> a number of debug tests like gcc.dg/debug/trivial.c fail when compiled
> using a stabs debug flag (-gstabs3 for example) and -mips16. While running
> the GNU simulator I get:
>
> mips-core: 1 byte read to unmapped address 0xffffe820 at 0xffffffff80020278
> program stopped with signal 10 (User defined signal 1).
> FAIL: gcc.dg/debug/trivial.c -gstabs3 -O execution test
>
> Since I don't actually care about STABS I was looking at undefining
> DBX_DEBUGGING_INFO in mips-mti-elf.h and mips-mti-linux.h which makes
> the failures a moot point for me since I would no longer run the tests
> with any -stabs flags.
>
> But I was wondering, are there any MIPS targets that do use stabs? If not
> maybe we should just remove the define of DBX_DEBUGGING_INFO from mips.h
> instead of undefing it just for my targets. Opinions?
Do you know why selecting stabs causes an execution failure?
That shouldn't happen regardless of whether the debug info itself is good.
I don't mind removing stabs from all MIPS targets, but I'd like to
understand why we get the execution failure first.
Richard
next prev parent reply other threads:[~2013-01-07 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:27 Steve Ellcey
2013-01-07 20:30 ` Richard Sandiford [this message]
2013-01-07 20:38 ` Richard Sandiford
2013-01-07 20:54 ` Steve Ellcey
2013-01-08 16:30 ` Steve Ellcey
2013-01-07 20:41 ` Steve Ellcey
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=87ip784tyl.fsf@talisman.default \
--to=rdsandiford@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sellcey@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).