public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kazu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/25125] [4.1 Regression] (short) ((int)(unsigned short) + (int)) is done in the wrong type
Date: Mon, 09 Jan 2006 04:37:00 -0000	[thread overview]
Message-ID: <20060109043714.13377.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25125-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from kazu at gcc dot gnu dot org  2006-01-09 04:37 -------
Subject: Bug 25125

Author: kazu
Date: Mon Jan  9 04:37:09 2006
New Revision: 109495

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=109495
Log:
gcc/
        PR tree-optimization/25125
        * convert.c (convert_to_integer): Don't narrow the type of a
        PLUX_EXPR or MINUS_EXPR if !flag_wrapv and the unwidened type
        is signed.

gcc/testsuite/
        PR tree-optimization/25125
        * gcc.dg/vect/vect-7.c, gcc.dg/vect/vect-reduc-2char.c,
        gcc.dg/vect/vect-reduc-2short.c: XFAIL.
        * gcc.c-torture/execute/pr25125.c: New.

Added:
    branches/gcc-4_1-branch/gcc/testsuite/gcc.c-torture/execute/pr25125.c
Modified:
    branches/gcc-4_1-branch/gcc/ChangeLog
    branches/gcc-4_1-branch/gcc/convert.c
    branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/vect/vect-7.c
    branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/vect/vect-reduc-2char.c
    branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/vect/vect-reduc-2short.c


-- 


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



  parent reply	other threads:[~2006-01-09  4:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27 17:39 [Bug c/25125] New: [4.1/4.2 " pinskia at gcc dot gnu dot org
2005-11-27 17:40 ` [Bug c/25125] " pinskia at gcc dot gnu dot org
2005-11-27 17:42 ` pinskia at gcc dot gnu dot org
2005-11-27 17:45 ` rguenth at gcc dot gnu dot org
2005-11-27 17:47 ` rguenth at gcc dot gnu dot org
2005-11-27 18:03 ` [Bug middle-end/25125] " pinskia at gcc dot gnu dot org
2005-11-28 21:48 ` janis at gcc dot gnu dot org
2005-12-04  4:21 ` pinskia at gcc dot gnu dot org
2005-12-17 17:26 ` kazu at gcc dot gnu dot org
2005-12-18 15:51 ` steven at gcc dot gnu dot org
2005-12-19 18:29 ` mmitchel at gcc dot gnu dot org
2005-12-19 18:29 ` mmitchel at gcc dot gnu dot org
2005-12-19 18:36 ` pinskia at gcc dot gnu dot org
2005-12-19 18:38 ` kazu at codesourcery dot com
2005-12-19 18:40 ` mark at codesourcery dot com
2005-12-26 23:00 ` kazu at gcc dot gnu dot org
2005-12-26 23:01 ` [Bug middle-end/25125] [4.1 " kazu at gcc dot gnu dot org
2005-12-27  1:07 ` danglin at gcc dot gnu dot org
2005-12-27  1:41 ` dave at hiauly1 dot hia dot nrc dot ca
2005-12-27 11:16 ` steven at gcc dot gnu dot org
2005-12-27 15:00 ` dave at hiauly1 dot hia dot nrc dot ca
2005-12-27 16:59 ` kazu at gcc dot gnu dot org
2005-12-27 17:06 ` dave at hiauly1 dot hia dot nrc dot ca
2005-12-27 19:27 ` dave at hiauly1 dot hia dot nrc dot ca
2005-12-27 22:35 ` dave at hiauly1 dot hia dot nrc dot ca
2006-01-09  4:37 ` kazu at gcc dot gnu dot org [this message]
2006-01-09  4:40 ` kazu at gcc dot gnu dot org
2006-01-09  4:42 ` kazu at gcc dot gnu dot org
2006-01-09  4:43 ` kazu at gcc dot gnu dot org
2006-02-26 14:44 ` dorit 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=20060109043714.13377.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).