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 c++/25950] [3.4/4.0/4.1 Regression] [DR 391] Reference binding and explicit copy constructors
Date: Wed, 25 Jan 2006 01:55:00 -0000	[thread overview]
Message-ID: <20060125015545.29416.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25950-11686@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pinskia at gcc dot gnu dot org  2006-01-25 01:55 -------
(In reply to comment #4)
> before you declare something as a regression, please make sure you do
> understand the real issues.  When you don't fully understand, please
> leave it alone and help somewhere else.  Thanks.

Well Marking things as regression is easy as it is just easy to test it on
different versions of GCC which I did.  Now figuring out what we should do here
is not up to me which is why I did not confirm it.  Now I read the DR and the
standard (well I did read it for the bug linked here) but it seems like the DR
only resolves one part of the question but it seems raise differnet questions
for me which is why I left it unconfirmed.  Should have I written this first,
maybe but then again you would have harped on me anyways.  If you noticed I
gave some back ground info on when the change happened and CCed the person who
changed it to get a clarification (in fact I said that in comment #2).  I
linked to the DR report so that people could easier access to it instead of
remembering the link each time when comming to this bug.  (and now this whole
thing is offtopic from the bug report).


-- 


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


  parent reply	other threads:[~2006-01-25  1:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 22:24 [Bug c++/25950] New: " hhinnant at apple dot com
2006-01-24 22:38 ` [Bug c++/25950] [DR 391] " pinskia at gcc dot gnu dot org
2006-01-24 22:48 ` [Bug c++/25950] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2006-01-24 22:51 ` hhinnant at apple dot com
2006-01-25  1:32 ` gdr at cs dot tamu dot edu
2006-01-25  1:55 ` pinskia at gcc dot gnu dot org [this message]
2006-01-25  2:05 ` hhinnant at apple dot com
2006-01-25  2:38 ` gdr at cs dot tamu dot edu
2006-01-25  2:41 ` [Bug c++/25950] [3.4/4.0/4.1] " gdr at gcc dot gnu dot org
2006-01-25  2:54 ` hhinnant at apple dot com
2006-01-25  3:03 ` [Bug c++/25950] [3.4/4.0/4.1 Regression] [DR 152] " pinskia at gcc dot gnu dot org
2006-01-25  3:10 ` gdr at cs dot tamu dot edu
2006-01-25  3:20 ` [Bug c++/25950] [3.4/4.0/4.1] [DR 392] " gdr at gcc dot gnu dot org
2006-01-25  3:20 ` [Bug c++/25950] [3.4/4.0/4.1 Regression] [DR 152] " gdr at cs dot tamu dot edu
2006-01-25  3:24 ` [Bug c++/25950] [3.4/4.0/4.1] [DR 392] " hhinnant at apple dot com
2006-01-25  3:28 ` [Bug c++/25950] [3.4/4.0/4.1] [DR 391] " gdr at gcc dot gnu dot org
2006-01-25  3:35 ` pinskia at gcc dot gnu dot org
2006-01-25  3:41 ` gdr at cs dot tamu dot edu
2006-01-25  6:46 ` mmitchel at gcc dot gnu dot org
2006-01-25 15:51 ` gdr at cs dot tamu dot edu
2006-02-24  0:30 ` mmitchel at gcc dot gnu dot org
2006-04-05  7:10 ` pinskia at gcc dot gnu dot org
2006-04-24 23:37 ` pinskia at gcc dot gnu dot org
2006-05-25  2:37 ` mmitchel at gcc dot gnu dot org
2006-07-12 23:11 ` pinskia at gcc dot gnu dot org
2006-08-25 17:41 ` pinskia at gcc dot gnu dot org
2007-02-14  9:09 ` mmitchel at gcc dot gnu dot org
2007-02-25 16:50 ` [Bug c++/25950] " pinskia at gcc dot gnu dot org
2007-03-12 22:00 ` pinskia at gcc dot gnu dot org
2007-10-22 19:14 ` jason at gcc dot gnu dot org
2007-10-24  3:46 ` jason at gcc dot gnu dot org
2007-11-03 13:40 ` jason at gcc dot gnu dot org
2008-07-04 19:32 ` jsm28 at gcc dot gnu dot org
2008-07-31  7:04 ` 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=20060125015545.29416.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).