public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48742] [4.5/4.6/4.7 Regression] Internal error in gimplify_expr
Date: Wed, 27 Apr 2011 07:14:00 -0000	[thread overview]
Message-ID: <bug-48742-4-ZjOISJRxvt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48742-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-04-27 07:05:56 UTC ---
Author: jakub
Date: Wed Apr 27 07:05:54 2011
New Revision: 173012

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173012
Log:
    PR c/48742
    * c-typeck.c (build_binary_op): Don't wrap arguments if
    int_operands is true.

    * gcc.c-torture/compile/pr48742.c: New test.

Added:
    branches/gcc-4_6-branch/gcc/testsuite/gcc.c-torture/compile/pr48742.c
Modified:
    branches/gcc-4_6-branch/gcc/ChangeLog
    branches/gcc-4_6-branch/gcc/c-typeck.c
    branches/gcc-4_6-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-04-27  7:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 19:23 [Bug c/48742] New: Internal error in glimplify_expr derek at knosof dot co.uk
2011-04-26  9:40 ` [Bug c/48742] [4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-04-26  9:42 ` rguenth at gcc dot gnu.org
2011-04-26 11:04 ` jakub at gcc dot gnu.org
2011-04-26 11:28 ` jakub at gcc dot gnu.org
2011-04-26 14:54 ` joseph at codesourcery dot com
2011-04-26 15:18 ` jakub at gcc dot gnu.org
2011-04-26 15:28 ` [Bug c/48742] [4.5/4.6/4.7 Regression] Internal error in gimplify_expr joseph at codesourcery dot com
2011-04-27  7:09 ` jakub at gcc dot gnu.org
2011-04-27  7:14 ` jakub at gcc dot gnu.org [this message]
2011-04-27  7:51 ` [Bug c/48742] [4.5 " jakub at gcc dot gnu.org
2011-05-03 16:35 ` jakub at gcc dot gnu.org
2011-05-03 17:36 ` jakub 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=bug-48742-4-ZjOISJRxvt@http.gcc.gnu.org/bugzilla/ \
    --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).