From: Jeff Law <law@redhat.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Sumanth Gundapaneni <Sumanth.Gundapaneni@kpitcummins.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>,
"rth@redhat.com" <rth@redhat.com>,
"Jayant R. Sonar" <Jayant.Sonar@kpitcummins.com>
Subject: Re: Internal Compiler Error in gen_rtx_SUBREG,at emit-rtl.c:776 in CR16
Date: Tue, 01 Feb 2011 15:22:00 -0000 [thread overview]
Message-ID: <4D482532.5000103@redhat.com> (raw)
In-Reply-To: <mcrbp2vixzv.fsf@google.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/01/11 08:19, Ian Lance Taylor wrote:
> Sumanth Gundapaneni <Sumanth.Gundapaneni@kpitcummins.com> writes:
>
>> If I compile the test case with "-O2 -fno-inline", there was no ICE related
>> to subreg. Is "cse_local" phase related to -finline optimization.
>
> Any RTL that can be created by inlining can also be created in other
> ways, so don't wory about inlining. You need to find out specifically
> what is creating that insn. I usually find it easiest to set a
> breakpoint on make_insn_raw with a breakpoint on cur_insn_uid (which is
> a macro, so you have to use the real expression) to find when the insn
> with a specific UID was created.
Tip: Place the breakpoint after the assignment:
INSN_UID (insn) = cur_insn_uid++;
And you don't have to know the "cur_insn_uid" magic...
b <line> if insn.u.fld[0].rt_int == <some #>
Breakpoints on an insn's UID become second nature quickly if you do a
lot of RTL debugging.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNSCUxAAoJEBRtltQi2kC7HJ0H/3X671YfS5DYy8ZtXFLJYy01
XiSPJRBHvlNCkIkUmogd/SvxoOyiIuLuH6+D267j+ikIVo/f1O5zE3ExdZIdu6CX
63gArkDInqr2darDtmX8cytVupJ55fkgsMgzZui153QAaXP7O/PzW8z4iyzbjT+u
GVaglb44+AbBz+NszWiExI8IVydub6C+G1OaqwQoQ5tYSvMxrxs7QJO6KmIzMgcG
0s0M7pRncq1HqydLGclLxbmdB7DzYkJmG81xJs5vbqypkjhTvGTYYXUvBblDwOy9
bhG7N0Bx1kOHF2woNSF0GyGGDWr8AD1z1myL38vwsnI6+ToZZAdCHsU68krifBU=
=cpR1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-02-01 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:38 Sumanth Gundapaneni
2011-01-31 19:21 ` Ian Lance Taylor
2011-02-01 9:08 ` Sumanth Gundapaneni
2011-02-01 15:19 ` Ian Lance Taylor
2011-02-01 15:22 ` Jeff Law [this message]
2011-02-04 14:15 ` Sumanth Gundapaneni
2011-02-04 15:51 ` Ian Lance Taylor
2011-02-04 16:25 ` Richard Henderson
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=4D482532.5000103@redhat.com \
--to=law@redhat.com \
--cc=Jayant.Sonar@kpitcummins.com \
--cc=Sumanth.Gundapaneni@kpitcummins.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=rth@redhat.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).