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/21959] [4.1 Regression] vrp miscompiles Ada front-end, drops loop exit test in well-defined wrap-around circumstances
Date: Fri, 17 Jun 2005 20:37:00 -0000	[thread overview]
Message-ID: <20050617203750.21522.qmail@sourceware.org> (raw)
In-Reply-To: <20050608123145.21959.pinskia@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-06-17 20:37 -------
(In reply to comment #10)
> > No because Ada front-end is creating:
> > signed_char <= 127 which is always true, removing this from fold would not
> > change the problem as it will still be optimized away.
> 
> Where do you see signed_char?  The type 0x556d9144 is unsigned.

Woops, I must have read something wrong.
This is still a bug in the VRP.
C Testcase:
unsigned char c[0xFF];
void f(void)
{
  unsigned char i;
  c[128] = 128;
  i = 0;
  while (1)
  {
    if (((signed char) i) < 0) break;
    c[i] = ' ';
    i++;
  }
}

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dnovillo at gcc dot gnu dot
                   |                            |org
          Component|ada                         |tree-optimization
            Summary|[4.1 Regression] Ada depends|[4.1 Regression] vrp
                   |on signed overflow          |miscompiles Ada front-end,
                   |                            |drops loop exit test in
                   |                            |well-defined wrap-around
                   |                            |circumstances


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


  parent reply	other threads:[~2005-06-17 20:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 12:32 [Bug ada/21959] New: [4.1 Regression] Ada depeends on signed overflow pinskia at gcc dot gnu dot org
2005-06-08 12:32 ` [Bug ada/21959] " pinskia at gcc dot gnu dot org
2005-06-09 11:59 ` [Bug ada/21959] [4.1 Regression] Ada depends " pluto at agmk dot net
2005-06-10 16:57 ` schwab at suse dot de
2005-06-10 17:00 ` schwab at suse dot de
2005-06-10 18:52 ` pinskia at gcc dot gnu dot org
2005-06-10 21:24 ` pluto at agmk dot net
2005-06-10 21:26 ` pinskia at gcc dot gnu dot org
2005-06-17 19:56 ` ebotcazou at gcc dot gnu dot org
2005-06-17 20:02 ` pinskia at gcc dot gnu dot org
2005-06-17 20:24 ` ebotcazou at gcc dot gnu dot org
2005-06-17 20:37 ` pinskia at gcc dot gnu dot org [this message]
2005-06-17 20:54 ` [Bug tree-optimization/21959] [4.1 Regression] vrp miscompiles Ada front-end, drops loop exit test in well-defined wrap-around circumstances pinskia at gcc dot gnu dot org
2005-06-21 19:49 ` pinskia at gcc dot gnu dot org
2005-06-21 21:06 ` laurent at guerby dot net
2005-06-27  5:02 ` pinskia at gcc dot gnu dot org
2005-06-27 11:42 ` dnovillo at gcc dot gnu dot org
2005-06-27 17:05 ` dnovillo at gcc dot gnu dot org
2005-06-27 19:41 ` dnovillo at gcc dot gnu dot org
2005-06-28  0:52 ` cvs-commit at gcc dot gnu dot org
2005-06-28  1:14 ` dnovillo at gcc dot gnu dot org
2005-06-28 18:04 ` 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=20050617203750.21522.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).