public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45522] VRP misses oppurtunity for statement folding.
Date: Fri, 03 Sep 2010 20:05:00 -0000	[thread overview]
Message-ID: <20100903200459.11296.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45522-176@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from hubicka at gcc dot gnu dot org  2010-09-03 20:04 -------
A related testcase where we fail to fold fundamentals[0]
typedef union tree_node *tree;
enum tree_code
{
  OFFSET_TYPE, ENUMERAL_TYPE, BOOLEAN_TYPE, POINTER_TYPE, FIXED_POINT_TYPE,
};
struct tree_base
{
  unsigned public_flag:1;
};
struct tree_decl_with_vis
{
  unsigned comdat_flag:1;
};
union tree_node
{
  struct tree_base base;
  struct tree_decl_with_vis decl_with_vis;
};
enum tree_index
{
    TI_LONG_DOUBLE_PTR_TYPE, TI_INTEGER_PTR_TYPE, TI_VOID_TYPE, TI_PTR_TYPE,
    TI_VA_LIST_FPR_COUNTER_FIELD, TI_BOOLEAN_TYPE, TI_FILEPTR_TYPE,
    TI_CURRENT_TARGET_PRAGMA, TI_CURRENT_OPTIMIZE_PRAGMA, TI_MAX
};
extern tree global_trees[TI_MAX];
emit_support_tinfos (void)
{
  static tree *const fundamentals[] = {
    &global_trees[TI_VOID_TYPE], &global_trees[TI_BOOLEAN_TYPE],
  };
  int ix;
  for (ix = 0; fundamentals[ix]; ix++)
    {
        {
          tree tinfo;
            {
              ((void) (!(((tinfo)->base.public_flag) && !(__extension__ (
                                                                          {
                                                                         
__typeof
                                                                         
(tinfo)
                                                                          __t
                                                                          =
                                                                         
(tinfo);
                                                                          __t;}
                                                          )->decl_with_vis.
                                                          comdat_flag)) ?
                       fancy_abort ("../../gcc/cp/rtti.c", 1529,
                                    __FUNCTION__), 0 : 0));
            }
        }
    }
}


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45522


  parent reply	other threads:[~2010-09-03 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 15:58 [Bug tree-optimization/45522] New: " hubicka at gcc dot gnu dot org
2010-09-03 15:59 ` [Bug tree-optimization/45522] " hubicka at gcc dot gnu dot org
2010-09-03 16:33 ` hubicka at gcc dot gnu dot org
2010-09-03 16:34 ` hubicka at gcc dot gnu dot org
2010-09-03 20:05 ` hubicka at gcc dot gnu dot org [this message]
2010-09-03 20:10 ` hubicka at gcc dot gnu dot org
2010-09-03 20:13 ` hubicka at gcc dot gnu dot org
2010-09-03 20:29 ` hubicka at gcc dot gnu dot org
2010-09-04  8:29 ` rguenther at suse dot de
2010-09-04 13:52 ` hubicka at gcc dot gnu dot org
2010-09-04 14:11 ` rguenther at suse dot de
2010-09-04 18:01 ` hubicka at gcc dot gnu dot org
     [not found] <bug-45522-4@http.gcc.gnu.org/bugzilla/>
2010-10-28 20:41 ` pinskia at gcc dot gnu.org

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=20100903200459.11296.qmail@sourceware.org \
    --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).