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/17064] -falias-noargument-global doesn't eliminate dead stores/loads
Date: Tue, 08 Feb 2005 00:29:00 -0000	[thread overview]
Message-ID: <20050207190006.12674.qmail@sourceware.org> (raw)
In-Reply-To: <20040817140542.17064.pbrook@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-02-07 19:00 -------
Another testcase this time for loads:
#include <stdlib.h>
int i;

void bar(void)
{
  i = 42;
}

int foo(int * p)
{
  int i = *p;
  bar ();
  return *p + i;/* This load is dead with -fargument-noalias-global.  */
}

int main()
{
  int t = 2;
  int t1;
  t1 = foo(&t);
  if (t1 != 4)
    abort();
  return 0;
}

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|-falias-noargument-global   |-falias-noargument-global
                   |doesn't eliminate dead      |doesn't eliminate dead
                   |stores                      |stores/loads


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


  parent reply	other threads:[~2005-02-07 19:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 14:05 [Bug tree-optimization/17064] New: -falias-noargument-global doesn't eliminate dead stores pbrook at gcc dot gnu dot org
2004-08-17 14:12 ` [Bug tree-optimization/17064] " dnovillo at gcc dot gnu dot org
2004-11-06 20:14 ` pinskia at gcc dot gnu dot org
2005-02-08  0:01 ` pinskia at gcc dot gnu dot org
2005-02-08  0:29 ` pinskia at gcc dot gnu dot org [this message]
2005-03-04  3:42 ` [Bug tree-optimization/17064] -falias-noargument-global doesn't eliminate dead stores/loads pinskia at gcc dot gnu dot org
2005-07-27 17:13 ` pinskia at gcc dot gnu dot org
2005-08-06 19:51 ` pinskia at gcc dot gnu dot org
     [not found] <bug-17064-6527@http.gcc.gnu.org/bugzilla/>
2005-10-05 13:21 ` pinskia at gcc dot gnu dot org
2006-01-10 20:35 ` pinskia at gcc dot gnu dot org
2006-01-10 20:36 ` pinskia at gcc dot gnu dot org
2006-01-16 17:11 ` pinskia at gcc dot gnu dot org
2006-01-26 17:51 ` pinskia at gcc dot gnu dot org
2006-01-26 17:51 ` pinskia at gcc dot gnu dot org
2006-01-26 18:15 ` pinskia at gcc dot gnu dot org
2006-01-29  4:32 ` pinskia at gcc dot gnu dot org
2006-01-31  0:49 ` dje at gcc dot gnu dot org
2006-01-31  1:11 ` pinskia at gcc dot gnu dot org
2009-04-03 11:57 ` rguenth at gcc dot gnu dot org
2010-07-13 10:21 ` steven at gcc dot gnu dot org
2010-07-13 11:11 ` rguenth at gcc dot gnu dot org
2010-07-13 11:27 ` steven at gcc dot gnu dot org
2010-07-13 13:30 ` 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=20050207190006.12674.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).