public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/30567] -fPIC -O3 optimizer bug
Date: Wed, 18 Apr 2007 21:11:00 -0000 [thread overview]
Message-ID: <20070418211127.10156.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30567-3137@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from hjl at lucon dot org 2007-04-18 22:11 -------
build_array_ref calls
return build_indirect_ref (cp_build_binary_op (PLUS_EXPR, ar, ind),
"array indexing");
with ar as pointer and ind as integer. cp_build_binary_op turns ind into
pointer and we wind up with
D.2455 = (long unsigned int) i;
D.2456 = D.2455 * 4;
D.2457 = (const int *) D.2456;
D.2458 = D.2454 + D.2457;
--
hjl at lucon dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at codesourcery dot com
GCC build triplet|i686-pc-linux-gnu |
GCC host triplet|i686-pc-linux-gnu |
GCC target triplet|i686-pc-linux-gnu |
Summary|-fPIC -O3 optimizer bug (32-|-fPIC -O3 optimizer bug
|bit target only) |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30567
next prev parent reply other threads:[~2007-04-18 21:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 0:08 [Bug c++/30567] New: -fPIC -O3 optimizer bug (32-bit target only) rwgk at yahoo dot com
2007-01-24 0:10 ` [Bug c++/30567] " rwgk at yahoo dot com
2007-01-24 6:57 ` pinskia at gcc dot gnu dot org
2007-01-28 20:03 ` rwgk at yahoo dot com
2007-02-03 20:42 ` rwgk at yahoo dot com
2007-02-11 4:08 ` bangerth at dealii dot org
2007-02-11 5:30 ` rwgk at yahoo dot com
2007-02-12 0:02 ` bangerth at dealii dot org
2007-02-12 5:23 ` rwgk at yahoo dot com
2007-02-12 15:48 ` rwgk at yahoo dot com
2007-02-12 16:03 ` bangerth at dealii dot org
2007-02-12 16:37 ` dberlin at gcc dot gnu dot org
2007-02-26 2:26 ` rwgk at yahoo dot com
2007-02-26 2:42 ` dberlin at dberlin dot org
2007-02-26 3:37 ` rwgk at yahoo dot com
2007-02-26 4:38 ` dberlin at gcc dot gnu dot org
2007-02-26 7:55 ` rwgk at yahoo dot com
2007-02-26 18:41 ` bangerth at dealii dot org
2007-04-18 19:00 ` hjl at lucon dot org
2007-04-18 19:02 ` hjl at lucon dot org
2007-04-18 20:47 ` hjl at lucon dot org
2007-04-18 21:11 ` hjl at lucon dot org [this message]
2007-04-18 21:47 ` [Bug c++/30567] -O3 optimizer bug rguenth at gcc dot gnu dot org
2007-04-18 21:56 ` [Bug tree-optimization/30567] " rguenth at gcc dot gnu dot org
2007-04-21 17:08 ` [Bug tree-optimization/30567] [4.2 Regression] " rguenth at gcc dot gnu dot org
2007-04-21 17:38 ` rguenth at gcc dot gnu dot org
2007-04-24 20:37 ` mmitchel at gcc dot gnu dot org
2007-04-25 2:14 ` dberlin at gcc dot gnu dot org
2007-04-25 13:22 ` rguenth at gcc dot gnu dot org
2007-04-25 13:43 ` rguenth at gcc dot gnu dot org
2007-04-25 14:04 ` rguenth at gcc dot gnu dot org
2007-04-25 15:32 ` rguenth at gcc dot gnu dot org
2007-04-25 15:42 ` rguenth at gcc dot gnu dot org
2007-04-25 16:01 ` dberlin at dberlin dot org
2007-04-25 16:13 ` rguenth at gcc dot gnu dot org
2007-04-25 18:45 ` dberlin at gcc dot gnu dot org
2007-04-26 9:02 ` rguenth at gcc dot gnu dot org
2007-04-26 11:16 ` rguenth at gcc dot gnu dot org
2007-04-26 11:16 ` rguenth at gcc dot gnu dot org
2007-04-26 15:50 ` 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=20070418211127.10156.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).