public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "felix dot nawothnig at t-online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18842] Weak optimization on global references
Date: Sun, 16 Jul 2006 14:23:00 -0000 [thread overview]
Message-ID: <20060716142316.6805.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18842-9734@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from felix dot nawothnig at t-online dot de 2006-07-16 14:23 -------
Don't know much about GCC internals but shouldn't this be a very trivial
enhancement? I know that this is FOSS so not to annoy anyone, just wondering
why it's still open after >1 year.
(In case someone is wondering why I care - this is the only one thing where
it's still faster to use macros instead of inline functions & references and
this access is a huge bottleneck in my application)
--
felix dot nawothnig at t-online dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |felix dot nawothnig at t-
| |online dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18842
next prev parent reply other threads:[~2006-07-16 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18842-9734@http.gcc.gnu.org/bugzilla/>
2006-03-05 21:30 ` pinskia at gcc dot gnu dot org
2006-07-16 14:23 ` felix dot nawothnig at t-online dot de [this message]
2006-07-16 20:36 ` rguenth at gcc dot gnu dot org
2009-04-22 22:02 ` pinskia at gcc dot gnu dot org
2004-12-05 8:55 [Bug c++/18842] New: " felix dot nawothnig at t-online dot de
2004-12-05 15:14 ` [Bug tree-optimization/18842] " pinskia at gcc dot gnu dot org
2004-12-05 19:11 ` felix dot nawothnig at t-online dot de
2004-12-05 19:15 ` pinskia 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=20060716142316.6805.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).