public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/22488] [4.1 Regression] push_fields_onto_fieldstack calculates offset incorrectly
Date: Tue, 04 Oct 2005 12:30:00 -0000	[thread overview]
Message-ID: <20051004123047.5374.qmail@sourceware.org> (raw)
In-Reply-To: <bug-22488-7559@http.gcc.gnu.org/bugzilla/>



------- Comment #38 from dberlin at gcc dot gnu dot org  2005-10-04 12:30 -------
As a 4.1 kludge, i can make the points-to analyzer do what it does for unions,
which is to glob everything to a single variable for those classes where it has
found two fields it thinks overlap.

This will lose alias precision, but it won't be worse than what 4.0 was.


-- 


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


       reply	other threads:[~2005-10-04 12:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22488-7559@http.gcc.gnu.org/bugzilla/>
2005-10-04 12:30 ` dberlin at gcc dot gnu dot org [this message]
2005-10-04 14:06 ` pinskia at gcc dot gnu dot org
2005-10-04 15:12 ` rguenth at gcc dot gnu dot org
2005-10-04 15:28 ` mark at codesourcery dot com
2005-10-04 21:05 ` jason at redhat dot com
2005-10-04 21:14 ` mark at codesourcery dot com
2005-10-06 19:38 ` cvs-commit at gcc dot gnu dot org
2005-10-08 17:26 ` dberlin at gcc dot gnu dot org
2005-10-09 15:45 ` [Bug c++/22488] " pinskia at gcc dot gnu dot org
2005-10-30 23:32 ` pinskia at gcc dot gnu dot org
2005-10-31 14:55 ` pinskia at gcc dot gnu dot org
2006-08-22 21:54 ` [Bug c++/22488] [4.1/4.2 " jason at gcc dot gnu dot org
2007-05-14 21:39 ` [Bug c++/22488] [4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-07-20  3:50 ` mmitchel at gcc dot gnu dot org
2007-10-09 19:29 ` mmitchel at gcc dot gnu dot org
2008-02-01 16:54 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:25 ` [Bug c++/22488] [4.1/4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-05-19 20:47 ` jason at gcc dot gnu dot org
2008-07-04 22:46 ` [Bug c++/22488] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-04-21 16:02 ` [Bug c++/22488] [4.2/4.3/4.4/4.5 " jakub at gcc dot gnu dot org
2009-07-22 10:35 ` jakub at gcc dot gnu dot org
2009-10-15 12:56 ` jakub at gcc dot gnu dot org
2010-01-21 13:19 ` [Bug c++/22488] [4.3/4.4/4.5 " jakub at gcc dot gnu dot org
2010-04-30  8:58 ` [Bug c++/22488] [4.3/4.4/4.5/4.6 " jakub at gcc dot gnu dot org
2005-07-14 14:16 [Bug tree-optimization/22488] New: ICE: in first_vi_for_offset, at tree-ssa-structalias.c:2585 with -O3 micis at gmx dot de
2005-09-28 15:57 ` [Bug tree-optimization/22488] [4.1 Regression] push_fields_onto_fieldstack calculates offset incorrectly mmitchel at gcc dot gnu dot org
2005-09-28 19:39 ` jason at redhat dot com
2005-09-28 20:16 ` dberlin at dberlin dot org
2005-09-28 20:29 ` mark at codesourcery dot com
2005-09-28 20:34 ` dberlin at dberlin dot org
2005-09-28 20:40 ` mark at codesourcery dot com
2005-09-29 17:20 ` jason at redhat dot com
2005-09-29 18:20 ` mark at codesourcery dot com

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=20051004123047.5374.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).