public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/38985]  New: [4.2/4.3/4.4 Regression] missing constraints for pointers accessed directly via their address
Date: Tue, 27 Jan 2009 11:15:00 -0000	[thread overview]
Message-ID: <bug-38985-7849@http.gcc.gnu.org/bugzilla/> (raw)

This testcase fails:

/* { dg-do compile } */
/* { dg-options "-O2 -fdump-tree-optimized" } */

int f(int *p)
{
  int a = *p;
  int *q = (int *)0xDEADBEE0;
  *q = 5;
  return *p == a;
}

/* { dg-final { scan-tree-dump-times " = \\\*p" 2 "optimized" } } */
/* { dg-final { scan-tree-dump-not "return 1" "optimized" } } */
/* { dg-final { cleanup-tree-dump "optimized" } } */


Unlike PR38984 it does not require -fno-delete-null-pointer-checks.


-- 
           Summary: [4.2/4.3/4.4 Regression] missing constraints for
                    pointers accessed directly via their address
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bonzini at gnu dot org
OtherBugsDependingO 38984
             nThis:


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


             reply	other threads:[~2009-01-27 11:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 11:15 bonzini at gnu dot org [this message]
2009-01-27 11:27 ` Andrew Thomas Pinski
2009-01-27 11:27 ` [Bug tree-optimization/38985] " pinskia at gmail dot com
2009-01-27 12:04 ` rguenth at gcc dot gnu dot org
2009-01-27 12:05 ` rguenth at gcc dot gnu dot org
2009-01-27 12:06 ` rguenth at gcc dot gnu dot org
2009-01-27 12:09 ` rguenth at gcc dot gnu dot org
2009-01-27 12:21 ` bonzini at gnu dot org
2009-01-27 12:29 ` bonzini at gnu dot org
2009-01-27 12:31 ` rguenth at gcc dot gnu dot org
2009-01-27 12:33 ` rguenth at gcc dot gnu dot org
2009-01-27 12:58 ` bonzini at gnu dot org
2009-01-27 13:05 ` rguenth at gcc dot gnu dot org
2009-01-27 13:18 ` bonzini at gnu dot org
2009-01-28 11:50 ` bonzini at gnu dot org
2009-01-28 12:08 ` rguenther at suse dot de
2009-01-28 21:38 ` rguenth at gcc dot gnu dot org
2009-03-31 21:08 ` [Bug tree-optimization/38985] [4.3/4.4/4.5 Regression] missing VOPs " jsm28 at gcc dot gnu dot org
2009-04-03 10:28 ` rguenth at gcc dot gnu dot org
2009-04-03 10:37 ` [Bug tree-optimization/38985] [4.3/4.4 " rguenth at gcc dot gnu dot org
2009-08-04 12:46 ` rguenth at gcc dot gnu dot org
2010-05-22 18:29 ` rguenth 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=bug-38985-7849@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).