public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/52372] [4.7 Regression] gcc.target/mips/mips16-attributes{,-4}.c SEGV in dwf_regno
Date: Mon, 14 Apr 2014 09:43:00 -0000 [thread overview]
Message-ID: <bug-52372-4-sjN39Lz2lB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52372-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52372
--- Comment #11 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #10)
> It still fails, but indeed for different targets: PR60102, PR57933. I'm not
> sure whether these are actually duplicates, though.
Yeah, despite dwf_regno appearing in all three backtraces, I think those
bugs are different from this one. In this case the problem was with
SWITCHABLE_TARGET. This bug was specifically about the failures
in the MIPS-specific mips16-attributes* tests.
prev parent reply other threads:[~2014-04-14 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 16:29 [Bug target/52372] New: " ro at gcc dot gnu.org
2012-02-24 16:38 ` [Bug target/52372] [4.7 regression] " ro at gcc dot gnu.org
2012-02-25 11:02 ` [Bug middle-end/52372] " rsandifo at gcc dot gnu.org
2012-02-27 10:42 ` rguenth at gcc dot gnu.org
2012-03-06 19:22 ` [Bug middle-end/52372] [4.7/4.8 " rsandifo at gcc dot gnu.org
2012-03-22 9:07 ` rguenth at gcc dot gnu.org
2012-06-14 8:35 ` rguenth at gcc dot gnu.org
2012-09-20 10:28 ` jakub at gcc dot gnu.org
2013-04-11 7:59 ` [Bug middle-end/52372] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-04-14 8:15 ` [Bug middle-end/52372] [4.7 Regression] " rsandifo at gcc dot gnu.org
2014-04-14 9:07 ` asolokha at gmx dot com
2014-04-14 9:43 ` rsandifo at gcc dot gnu.org [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=bug-52372-4-sjN39Lz2lB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).