public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18040] [4.0 Regression] ICE in for_each_index, at tree-ssa-loop-im.c:178
Date: Sun, 17 Oct 2004 22:19:00 -0000	[thread overview]
Message-ID: <20041017221939.25198.qmail@sourceware.org> (raw)
In-Reply-To: <20041017123619.18040.aj@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-10-17 22:19 -------
Here is another example which works:
int PyObject_IsTrue();
struct object_base
{
    void ptr() const;
};
struct object : public object_base
{
  void ptr1() const;
  typedef void (object::*bool_type)() const;
  inline operator bool_type() const { return PyObject_IsTrue() ? &object_base::ptr : &object::ptr1; }
};
void f();
void g (void)
{
    for (unsigned n = 0; n < 100; ++n)
    {
        object kv;
        if (kv)
          f();
    }
}

And another which does not:
int PyObject_IsTrue();
struct object_base
{
    void ptr() const;
  void ptr1() const;
};
struct object : public object_base
{
  typedef void (object::*bool_type)() const;
  inline operator bool_type() const { return PyObject_IsTrue() ? &object_base::ptr : &object::ptr1; }
};
void f();
void g (void)
{
    for (unsigned n = 0; n < 100; ++n)
    {
        object kv;
        if (kv)
          f();
    }
}

-- 


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


  parent reply	other threads:[~2004-10-17 22:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 12:36 [Bug middle-end/18040] New: " aj at gcc dot gnu dot org
2004-10-17 12:37 ` [Bug middle-end/18040] " aj at gcc dot gnu dot org
2004-10-17 13:06 ` kazu at cs dot umass dot edu
2004-10-17 13:34 ` [Bug middle-end/18040] [4.0 Regression] " giovannibajo at libero dot it
2004-10-17 14:47 ` [Bug tree-optimization/18040] " pinskia at gcc dot gnu dot org
2004-10-17 16:01 ` rakdver at gcc dot gnu dot org
2004-10-17 16:11 ` pinskia at gcc dot gnu dot org
2004-10-17 16:17 ` pinskia at gcc dot gnu dot org
2004-10-17 16:23 ` rakdver at gcc dot gnu dot org
2004-10-17 16:30 ` pinskia at gcc dot gnu dot org
2004-10-17 19:18 ` rakdver at gcc dot gnu dot org
2004-10-17 22:06 ` pinskia at gcc dot gnu dot org
2004-10-17 22:17 ` pinskia at gcc dot gnu dot org
2004-10-17 22:19 ` pinskia at gcc dot gnu dot org [this message]
2004-11-27 21:17 ` neroden at gcc dot gnu dot org
2004-11-27 21:20 ` pinskia at gcc dot gnu dot org
2004-12-10 16:54 ` pinskia at gcc dot gnu dot org
2004-12-12  3:05 ` pinskia at gcc dot gnu dot org
2004-12-12 16:45 ` cvs-commit at gcc dot gnu dot org
2004-12-12 16:46 ` pinskia at gcc dot gnu dot 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=20041017221939.25198.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).