public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kalmquist1 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66355] defining a constructor inhibits optimization
Date: Wed, 10 Jun 2015 01:04:00 -0000 [thread overview]
Message-ID: <bug-66355-4-37dQQN9oiM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66355-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66355
kalmquist1 at hotmail dot com <kalmquist1 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from kalmquist1 at hotmail dot com <kalmquist1 at hotmail dot com> ---
Thanks to the pointer provided by Marc Glisse, I found that this issue was
reported back in 2001, in PR 4131.
*** This bug has been marked as a duplicate of bug 4131 ***
prev parent reply other threads:[~2015-06-10 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 22:01 [Bug c++/66355] New: " kalmquist1 at hotmail dot com
2015-06-01 8:43 ` [Bug c++/66355] " redi at gcc dot gnu.org
2015-06-06 8:19 ` glisse at gcc dot gnu.org
2015-06-10 1:04 ` kalmquist1 at hotmail dot com [this message]
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-66355-4-37dQQN9oiM@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).