From: Jan Hubicka <hubicka@ucw.cz>
To: Kaz Kojima <kkojima@rr.iij4u.or.jp>
Cc: jh@suse.cz, gcc-patches@gcc.gnu.org
Subject: Re: RTL sharing tester (for testing)
Date: Thu, 28 Jun 2007 04:24:00 -0000 [thread overview]
Message-ID: <20070627232715.GD15535@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20070628.081214.68144053.kkojima@rr.iij4u.or.jp>
> Jan Hubicka <jh@suse.cz> wrote:
> > The problem with is that the nature of problem is very target specific.
> > All the remaining problems are either very weird side cases, or target
> > issues. This is why I am posting the patch so people can test it on
> > their favorite development platform.
>
> FYI, I've tried your tester on SH and got an error which looks
> similar to PPC's one:
>
> ../../../../../../TMP/trunk/libjava/classpath/native/fdlibm/e_exp.c:164: error: invalid rtl sharing found in the insn
> (insn:HI 207 303 256 24 ../../../../../../TMP/trunk/libjava/classpath/native/fdlibm/e_exp.c:162 (parallel [
> (set (reg/v:DF 76 fr12 [orig:180 x ] [180])
> (mult:DF (reg/v:DF 76 fr12 [orig:180 x ] [180])
> (reg:DF 66 fr2)))
> (use (reg/v:PSI 151 ))
> ]) 340 {muldf3_i} (expr_list:REG_DEAD (reg/v:PSI 151 )
> (expr_list:REG_DEAD (subreg:DF (reg/v:DI 1 r1 [orig:178 sh_u ] [178]) 0) (expr_list:REG_DEAD (reg:DF 66 fr2)
> (expr_list:REG_EQUAL (mult:DF (subreg:DF (reg/v:DI 1 r1 [orig:178 sh_u ] [178]) 0)
> (const_double:DF 9.33263618503218878990089544723817169617091446372e-302 [0x0.8p-999]))
> (nil))))))
> ../../../../../../TMP/trunk/libjava/classpath/native/fdlibm/e_exp.c:164: error: shared rtx
> (subreg:DF (reg/v:DI 1 r1 [orig:178 sh_u ] [178]) 0)
> ../../../../../../TMP/trunk/libjava/classpath/native/fdlibm/e_exp.c:164: internal compiler error: internal consistency failure
>
> and SH bootstraps without Java. As an experiment, I've tried a one
> liner:
>
> --- ORIG/trunk/gcc/df-problems.c 2007-06-22 09:16:00.000000000 +0900
> +++ TMP/trunk/gcc/df-problems.c 2007-06-26 13:53:47.000000000 +0900
> @@ -3713,7 +3713,8 @@ df_set_note (enum reg_note note_type, rt
> }
>
> /* Did not find the note. */
> - REG_NOTES (insn) = alloc_EXPR_LIST (note_type, reg, REG_NOTES (insn));
> + REG_NOTES (insn) = alloc_EXPR_LIST (note_type, copy_rtx (reg),
> + REG_NOTES (insn));
> return old;
> }
>
> Then the above error on SH went away. This one liner may be
> an overkill, but I hope that this experiment will help experts
> to narrow down the problem.
Actually this seems like a correct fix for me. In fact I was just
looking into instance of identical problem on PPC bootstrap (different
file, same directory of libjava :). We will copy iff the reg actually
is subreg and in that case we are required to copy.
I am re-testing PPC targets with this fix in now.
Thanks a lot!
Honza
>
> Regards,
> kaz
next prev parent reply other threads:[~2007-06-27 23:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 3:43 Jan Hubicka
2007-06-27 15:55 ` Kenneth Zadeck
2007-06-27 18:17 ` Diego Novillo
2007-06-27 21:43 ` Jan Hubicka
2007-06-28 2:02 ` Kaz Kojima
2007-06-28 4:24 ` Jan Hubicka [this message]
2007-06-28 8:11 ` Paolo Bonzini
2007-06-28 17:16 ` Kenneth Zadeck
2007-06-28 18:26 ` Jan Hubicka
2007-06-28 19:57 ` Kenneth Zadeck
2007-06-28 20:27 ` Richard Sandiford
2007-06-29 8:29 ` Richard Sandiford
2007-06-29 12:11 ` Kenneth Zadeck
2007-06-29 13:35 ` Paolo Bonzini
2007-06-29 13:37 ` Bernd Schmidt
2007-06-29 13:39 ` Jan Hubicka
2007-06-29 16:55 ` Richard Sandiford
2007-07-13 10:15 ` RFA: Stop df from generating SUBREG REG_NOTES Richard Sandiford
2007-07-25 22:50 ` Richard Sandiford
2007-07-27 0:01 ` Ian Lance Taylor
2007-06-28 20:19 ` RTL sharing tester (for testing) Paolo Bonzini
2007-06-27 23:06 ` Mark Mitchell
2007-06-27 23:06 ` Jan Hubicka
2007-06-27 23:12 ` Eric Christopher
2007-06-28 0:48 ` Jan Hubicka
2007-06-28 22:24 ` Eric Christopher
2007-06-29 23:14 ` Graham Stott
2007-06-30 0:17 ` Jan Hubicka
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=20070627232715.GD15535@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=kkojima@rr.iij4u.or.jp \
/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).