public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/50489] [UPC/IA64] mis-schedule of MEM ref with -ftree-vectorize and -fschedule-insns2
Date: Sun, 25 Sep 2011 12:26:00 -0000	[thread overview]
Message-ID: <bug-50489-4-xBa2JCk7D6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50489-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-09-25 12:13:44 UTC ---
  D.3059_11 = VIEW_CONVERT_EXPR<shared [8] struct foo[1] *>(D.3058);

looks like bogus IL to me.  You view D.3058, a struct of size 16, as
a pointer (of size 8).  I suppose you want to load D.3058.vaddr here?

  D.3060_12 = (shared [8] struct foo *) D.3059_11;
  D.3061_13 = VIEW_CONVERT_EXPR<struct upc_shared_ptr_t>(D.3060_12).phase;

looks bogus IL to me.  It views the pointer(!?) D.3060_12 as being a
struct upc_shared_ptr_t and extracts a value that is not within that
pointer.

But maybe I'm missing something because I don't recognize that 'shared [8]'
qualification.

Do you want to dereference D.3060_12 (D.3058.vaddr) here?

That said, I wonder why you don't trip over tree-cfg.c verification
of VIEW_CONVERT_EXPR as TYPE_SIZE (TREE_TYPE (D.3060_12)) != TYPE_SIZE (struct
upc_shared_ptr_t).

Please try to avoid using VIEW_CONVERT_EXPRs completely unless you know
exactly what you are doing.


  parent reply	other threads:[~2011-09-25 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 19:22 [Bug rtl-optimization/50489] New: " gary at intrepid dot com
2011-09-22 19:30 ` [Bug rtl-optimization/50489] " gary at intrepid dot com
2011-09-22 19:33 ` gary at intrepid dot com
2011-09-23 10:11 ` amonakov at gcc dot gnu.org
2011-09-23 17:59 ` gary at intrepid dot com
2011-09-25 12:26 ` rguenth at gcc dot gnu.org [this message]
2011-09-25 20:06 ` gary at intrepid dot com
2011-10-17  3:04 ` gary at intrepid dot com
2012-08-20 20:54 ` olegendo at gcc dot gnu.org
2024-03-28  4:31 ` pinskia at gcc dot gnu.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=bug-50489-4-xBa2JCk7D6@http.gcc.gnu.org/bugzilla/ \
    --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).