public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18842] Weak optimization on global references
Date: Sun, 05 Dec 2004 19:15:00 -0000 [thread overview]
Message-ID: <20041205191510.23830.qmail@sourceware.org> (raw)
In-Reply-To: <20041205085537.18842.felix.nawothnig@t-online.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-05 19:15 -------
(In reply to comment #5)
> Diagnostics? Both files are 100% valid C++ - but since the C++ standard doesn't
> enforce implementation of references as pointers they cause ABI-defined (?)
> behaviour at/after linkage, just as...
Yes both files are valid C++ but when you link them together they become invalid C++ and yes
the C++ defines this as invalid with no diagnostic required. In fact your example is also invalid C++
but since the standard says we don't have to provide diagnostic as it is a hard problem to actually
provide the diagnostic.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18842
next prev parent reply other threads:[~2004-12-05 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 8:55 [Bug c++/18842] New: " felix dot nawothnig at t-online dot de
2004-12-05 8:58 ` [Bug c++/18842] " felix dot nawothnig at t-online dot de
2004-12-05 14:53 ` steven at gcc dot gnu dot org
2004-12-05 15:00 ` pinskia at gcc dot gnu dot org
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 [this message]
[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
2006-07-16 20:36 ` rguenth at gcc dot gnu dot org
2009-04-22 22:02 ` 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=20041205191510.23830.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).