public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/23659] Should able to add dereferencing (statements with VUSE) without rerunning may_alias Date: Wed, 01 Mar 2006 14:30:00 -0000 [thread overview] Message-ID: <20060301143053.21016.qmail@sourceware.org> (raw) In-Reply-To: <bug-23659-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from dnovillo at gcc dot gnu dot org 2006-03-01 14:30 ------- (In reply to comment #4) > are you still working on this PR? > Yes. In fact, it's one of the kind of manipulations that drove the design decisions in memory SSA. > I think something similar to the attached patch should fix the problem -- it > makes us remember alias class --> TMT mapping globally, and uses it to set up > TMT's for the new pointers. Could you please comment on whether you consider > this the right approach, or propose an alternative one? > Whenever a new pointer symbol is introduced, it should receive a type tag. This type tag is then assigned a set of aliases (or not, depending on context). In fact, my plan is for these manually added type tags to be marked so that subsequent alias passes don't affect them. This should help the vectorizer and other passes introduce a pointer symbol with a specific set of points-to aliases that the aliaser may not have a chance of compute so accurately otherwise. > On a side note, things like this might become even more difficult with the new > memory ssa approach. > Huh. What makes you think that? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23659
next prev parent reply other threads:[~2006-03-01 14:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23659-6528@http.gcc.gnu.org/bugzilla/> 2005-11-12 5:32 ` pinskia at gcc dot gnu dot org 2006-03-01 12:10 ` rakdver at gcc dot gnu dot org 2006-03-01 14:30 ` dnovillo at gcc dot gnu dot org [this message] [not found] <bug-23659-4@http.gcc.gnu.org/bugzilla/> 2021-05-04 12:04 ` rguenth at gcc dot gnu.org 2005-08-31 17:00 [Bug tree-optimization/23659] New: " pinskia at gcc dot gnu dot org 2005-08-31 17:02 ` [Bug tree-optimization/23659] " pinskia at gcc dot gnu dot org 2005-08-31 21:41 ` steven at gcc dot gnu dot org 2005-08-31 21:57 ` dnovillo 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=20060301143053.21016.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).