From: vikram1729 <vsp1729@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: GCC 4.9.2 dwarf problem
Date: Fri, 10 Jul 2015 09:03:00 -0000 [thread overview]
Message-ID: <1436518982375-1167279.post@n5.nabble.com> (raw)
Hi
I am porting gcc 4.9.2 for a custom processor. Seems that debugging info is
not generating properly.
I am getting ICE in gcc 4.9.2 at
gcc/dwarf2cfi.c::dwarf2out_frame_debug_expr::1663
=============================================================
/* Rule 9 */
else if (GET_CODE (src) == LO_SUM
&& CONST_INT_P (XEXP (src, 1)))
{
cur_trace->cfa_temp.reg = dwf_regno (dest);
cur_trace->cfa_temp.offset = INTVAL (XEXP (src, 1));
}
else
gcc_unreachable ();
}
break;
/* Rule 6 */
case CONST_INT:
=================================================
Actually in my case the condition comes like this
(REG_P(XEXP(src, 0)) && REG_P (XEXP (src, 1)))
which is not in any rule. What to do. Any help please.
-vikram
--
View this message in context: http://gcc.1065356.n5.nabble.com/GCC-4-9-2-dwarf-problem-tp1167279.html
Sent from the gcc - Help mailing list archive at Nabble.com.
reply other threads:[~2015-07-10 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1436518982375-1167279.post@n5.nabble.com \
--to=vsp1729@gmail.com \
--cc=gcc-help@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).