public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/16306] [4.2/4.3/4.4 Regression] restrict and copying pointers problem Date: Wed, 01 Oct 2008 14:33:00 -0000 [thread overview] Message-ID: <20081001143229.24336.qmail@sourceware.org> (raw) In-Reply-To: <bug-16306-1008@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from rguenth at gcc dot gnu dot org 2008-10-01 14:32 ------- This is effectively a dup of PR14187. We fail to track what pointers are based on a restrict pointer. *** This bug has been marked as a duplicate of 14187 *** -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16306
prev parent reply other threads:[~2008-10-01 14:33 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-16306-1008@http.gcc.gnu.org/bugzilla/> 2005-10-12 20:58 ` [Bug tree-optimization/16306] [4.0/4.1 " steven at gcc dot gnu dot org 2005-10-12 20:58 ` steven at gcc dot gnu dot org 2005-10-22 3:12 ` pinskia at gcc dot gnu dot org 2005-10-30 22:41 ` mmitchel at gcc dot gnu dot org 2006-03-11 3:20 ` [Bug tree-optimization/16306] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2007-01-18 2:57 ` [Bug tree-optimization/16306] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org 2007-01-21 21:48 ` pinskia at gcc dot gnu dot org 2007-02-14 9:34 ` mmitchel at gcc dot gnu dot org 2007-12-28 13:36 ` pinskia at gcc dot gnu dot org 2008-07-04 16:33 ` [Bug tree-optimization/16306] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-10-01 14:33 ` rguenth at gcc dot gnu dot org [this message]
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=20081001143229.24336.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: linkBe 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).