This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c++/3628: "using std::rel_ops" blows up std::vector
- To: gcc-gnats at gcc dot gnu dot org
- Subject: c++/3628: "using std::rel_ops" blows up std::vector
- From: Richard dot Kreckel at GiNaC dot DE
- Date: 9 Jul 2001 20:50:34 -0000
- Cc: Joe Buck <jbuck at racerx dot synopsys dot com>
- Reply-To: Richard dot Kreckel at GiNaC dot DE
>Number: 3628
>Category: c++
>Synopsis: "using std::rel_ops" blows up std::vector
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Mon Jul 09 13:56:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Richard Kreckel
>Release: gcc version 3.0 (release)
>Organization:
>Environment:
Debian GNU/Linux (potato)
>Description:
This bug is related to c++/2405, which has been closed already.
Indeed, the example given there seems to be fixed. But something
similar can be easily triggered with the GCC-3.0 release by
this example:
#include <iostream>
#include <vector>
#include <utility>
using namespace std;
using namespace std::rel_ops;
int main(void)
{
vector<int> iv;
iv.push_back(0);
iv.push_back(1);
//...
for (vector<int>::iterator i=iv.begin(); i!=iv.end(); ++i) { }
}
Q: Does this qulify as a regression? After all in gcc-2.95 there was no
such thing as namespace rel_ops and the applications worked fine.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: