public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36713] [4.4 regression] r137252 breaks -O2 optimization on x86_64-unknown-linux-gnu
Date: Thu, 03 Jul 2008 11:42:00 -0000	[thread overview]
Message-ID: <20080703114213.31802.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36713-13648@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from dfranke at gcc dot gnu dot org  2008-07-03 11:42 -------
Differences in *.optimized dumps seem to be variable renaming only, e.g.
  -  temp.1140 = tdata->p;
  +  temp.1137 = tdata->p;

Differences in *.alias seems to be mostly of the kind:
  -PARM_NOALIAS.895 = &ANYTHING
  +PARM_NOALIAS.895 = &ESCAPED

However, I also found:
  -PARM_NOALIAS.895 = { ANYTHING ESCAPED NONLOCAL }
  -D.3410_6 = same as thread_data
  -thread_data = { ANYTHING }
  -D.3411_7 = same as thread_data
  +PARM_NOALIAS.895 = { ESCAPED NONLOCAL }
  +D.3410_6 = same as derefaddrtmp.893
  +thread_data = same as derefaddrtmp.893         <---- ?!?
  +D.3411_7 = same as derefaddrtmp.893

which might hint at the problem: the variable thread_data is an allocated
POINTER to a vector of structures (which hold more pointers), public within a
module. USE-ing it, makes it (sort of) local to the function. Most (>80% of
all) changes in *.optimized where in the one source file that uses this module
...

Richard, would this fit the bill?


-- 


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


  parent reply	other threads:[~2008-07-03 11:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  9:09 [Bug target/36713] New: " dfranke at gcc dot gnu dot org
2008-07-03  9:13 ` [Bug target/36713] " rguenther at suse dot de
2008-07-03  9:15 ` dfranke at gcc dot gnu dot org
2008-07-03  9:43 ` rguenther at suse dot de
2008-07-03  9:54 ` franke dot daniel at gmail dot com
2008-07-03 10:09 ` rguenther at suse dot de
2008-07-03 10:41 ` dfranke at gcc dot gnu dot org
2008-07-03 11:42 ` dfranke at gcc dot gnu dot org [this message]
2008-07-03 11:50 ` rguenther at suse dot de
2008-07-03 12:00 ` dfranke at gcc dot gnu dot org
2008-07-03 12:04 ` rguenther at suse dot de
2008-07-03 12:46 ` dfranke at gcc dot gnu dot org
2008-07-03 12:55 ` rguenther at suse dot de
2008-07-03 13:01 ` dfranke at gcc dot gnu dot org
2008-07-03 13:11 ` rguenther at suse dot de
2008-07-03 19:00 ` dfranke at gcc dot gnu dot org
2008-07-03 19:27 ` rguenther at suse dot de
2008-07-03 19:34 ` franke dot daniel at gmail dot com
2008-07-03 19:45 ` rguenther at suse dot de
2008-07-04 15:07 ` rguenth at gcc dot gnu dot org
2008-07-04 15:07 ` rguenth at gcc dot gnu dot org
2008-07-04 15:47 ` rguenth at gcc dot gnu dot org
2008-07-04 21:36 ` dfranke at gcc dot gnu dot org
2008-07-06 13:30 ` rguenth at gcc dot gnu dot org
2008-07-07 15:12 ` rguenth at gcc dot gnu dot org
2008-07-07 15:17 ` 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=20080703114213.31802.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).