public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/37417] [4.4 Regression] error: type mismatch in binary expression, verify_gimple failed
Date: Tue, 09 Sep 2008 16:42:00 -0000	[thread overview]
Message-ID: <20080909164120.6769.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37417-12387@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jakub at gcc dot gnu dot org  2008-09-09 16:41 -------
FE bug:
tree
array_type_nelts_top (tree type)
{
  return fold_build2 (PLUS_EXPR, sizetype,
                      array_type_nelts (type),
                      integer_one_node);
}
Should use size_one_node instead.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |jakub at gcc dot gnu dot org
                   |dot org                     |
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2008-09-08 21:05:56         |2008-09-09 16:41:19
               date|                            |


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


  parent reply	other threads:[~2008-09-09 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  8:47 [Bug middle-end/37417] New: " tbm at cyrius dot com
2008-09-08  8:49 ` [Bug middle-end/37417] " tbm at cyrius dot com
2008-09-08  8:54 ` tbm at cyrius dot com
2008-09-08 10:09 ` tbm at cyrius dot com
2008-09-08 21:07 ` [Bug c++/37417] " pinskia at gcc dot gnu dot org
2008-09-09 16:42 ` jakub at gcc dot gnu dot org [this message]
2008-09-09 20:41 ` jsm28 at gcc dot gnu dot org
2008-09-09 22:11 ` jakub at gcc dot gnu dot org
2008-09-09 22:15 ` jakub 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=20080909164120.6769.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).