public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: law@redhat.com
Cc: Jan Hubicka <jh@suse.cz>, Jan Hubicka <hubicka@ucw.cz>,
	Richard Henderson <rth@redhat.com>,
	gcc@gcc.gnu.org
Subject: Re: Tree sharing issues...
Date: Wed, 19 Nov 2003 22:31:00 -0000	[thread overview]
Message-ID: <20031119222038.GO11681@kam.mff.cuni.cz> (raw)
In-Reply-To: <200311192216.hAJMGPEx012475@speedy.slc.redhat.com>

> In message <20031119221355.GN11681@kam.mff.cuni.cz>, Jan Hubicka writes:
>  >> > On Wed, Nov 19, 2003 at 08:01:52PM +0100, Jan Hubicka wrote:
>  >> > > I am almost done with verify_stmts except for tree sharing, as I am
>  >> > > still not clear about the tree sharing rules.  (Did I mentioned it in
>  >> > > original email?)
>  >> > 
>  >> > Yes.  I don't know anything about tree sharing rules.  I expect we
>  >> > can't share much.
>  >> 
>  >> I think we do pretty heavy shaing via CCP that does move around the
>  >> constant PLUS_EXPRs and friends.  I am not even aware of way to copy
>  >> tree expressions.
>  >> I wrote the code for testing and will run it once my other bootstrap
>  >> finish and come back with results.
>  >OK, first possitive in bootstrap is not very far:
>  >stage1/xgcc -Bstage1/ -B/usr/local/i686-pc-linux-gnu/bin/ -c   -g -O2
>  >-DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes
>  >-Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition
>  >-Werror -fno-common   -DHAVE_CONFIG_H -DGENERATOR_FILE    -I. -I.
>  >-I../../gcc -I../../gcc/.
>  >-I../../gcc/../include   ../../gcc/gengtype.c -o gengtype.o
>  >(const char *)"*x";
>  >
>  >../../gcc/gengtype.c: In function `write_local_func_for_structure':
>  >
>  >../../gcc/gengtype.c:2184: error: Wrong sharing of tree nodes
>  >../../gcc/gengtype.c:2184: internal compiler error: verify_stmts failed.
>  >
>  >
>  >A shared NOP.  Is this valid? If not, how to duplicate the nodes in CCP?
> Not enough context to know if it's valid.
You may see dump above:
(const char *)"*x";
It is constant.
> 
> I would expect a NOP of a constant to be shared since that's still a
> constant and we generally try to share constants.

OK, I will extend my sharing test by is_gimple_min_invariant.  Does that
look right?

Honza
> 
> jeff

  reply	other threads:[~2003-11-19 22:20 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 18:38 Tree-SSA self checking infrastructure Jan Hubicka
2003-11-19 18:43 ` law
2003-11-19 18:48   ` Andrew MacLeod
2003-11-19 18:56     ` Jan Hubicka
2003-11-19 19:04       ` Andrew MacLeod
2003-11-19 19:39         ` law
2003-11-19 19:01     ` law
2003-11-19 19:12       ` Andrew MacLeod
2003-11-19 20:16         ` law
2003-11-19 18:51   ` Jan Hubicka
2003-11-19 19:09     ` law
2003-11-19 19:14       ` Jan Hubicka
2003-11-19 19:47         ` law
2003-11-19 20:23           ` Andrew MacLeod
2003-11-19 20:29             ` Andrew MacLeod
2003-11-19 20:36             ` Andrew MacLeod
2003-11-19 20:40               ` Andrew MacLeod
2003-11-19 22:12                 ` Andrew MacLeod
2003-11-19 22:46                   ` law
2003-11-19 22:59                 ` law
2003-11-19 20:47           ` Jan Hubicka
2003-11-19 21:13             ` law
2003-11-19 21:18               ` Jan Hubicka
2003-11-19 21:45                 ` law
2003-11-19 21:49                   ` Andrew MacLeod
2003-11-19 21:23           ` Richard Henderson
2003-11-19 21:34             ` Jan Hubicka
2003-11-19 21:44             ` law
2003-11-19 21:45               ` Jan Hubicka
2003-11-19 21:51                 ` law
2003-11-19 22:13                   ` Andrew MacLeod
2003-11-20  0:14                     ` Diego Novillo
2003-11-19 22:15                   ` Jan Hubicka
2003-11-19 22:56                     ` law
2003-11-19 21:58               ` Richard Henderson
2003-11-19 19:34       ` Jan Hubicka
2003-11-19 20:02         ` law
2003-11-19 20:49           ` Jan Hubicka
2003-11-19 21:01             ` law
2003-11-19 21:22               ` Jan Hubicka
2003-11-19 21:28             ` Richard Henderson
2003-11-21  6:35   ` Jan Hubicka
2003-11-21  8:10     ` law
2003-11-21 12:31       ` Jan Hubicka
2003-11-19 19:06 ` Richard Henderson
2003-11-19 19:09   ` Jan Hubicka
2003-11-19 21:36     ` Richard Henderson
2003-11-19 21:45       ` Jan Hubicka
2003-11-19 21:47         ` Richard Henderson
2003-11-19 22:23         ` Tree sharing issues Jan Hubicka
2003-11-19 22:27           ` law
2003-11-19 22:31             ` Jan Hubicka [this message]
2003-11-19 22:50               ` law
2003-11-19 23:02                 ` Jan Hubicka
2003-11-19 23:02                   ` law
2003-11-19 23:08                     ` Jan Hubicka
2003-11-19 23:12                       ` law
2003-11-19 23:20                         ` Jan Hubicka
2003-11-19 23:23                           ` law
2003-11-19 23:27                             ` Jan Hubicka
2003-11-19 23:30                               ` Richard Henderson
2003-11-20  0:33                                 ` Diego Novillo
2003-11-20  0:34                                   ` Jan Hubicka
2003-11-20  0:46                                     ` Diego Novillo
2003-11-20  4:22                                       ` law
2003-11-20  6:17                                         ` Diego Novillo
2003-11-19 23:33                               ` law
2003-11-19 23:34                                 ` Richard Henderson
2003-11-20  0:02                                   ` Jan Hubicka
2003-11-19 23:46                                 ` Jan Hubicka
2003-11-20 18:38                                   ` law
2003-11-20  0:37                               ` Diego Novillo
2003-11-20  0:41                                 ` Jan Hubicka
2003-11-20  1:26                                 ` Jan Hubicka
2003-11-20  0:20                   ` Diego Novillo
2003-11-20  0:29                     ` Jan Hubicka
2003-11-20  0:55                       ` Diego Novillo
2003-11-20  0:15         ` Tree-SSA self checking infrastructure Diego Novillo
2003-11-20  0:21           ` Jan Hubicka
2003-11-20  9:31             ` 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=20031119222038.GO11681@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=law@redhat.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).