From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18248 invoked by alias); 3 Jul 2002 21:36:04 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 18220 invoked by uid 71); 3 Jul 2002 21:36:02 -0000 Date: Wed, 03 Jul 2002 14:36:00 -0000 Message-ID: <20020703213602.18215.qmail@sources.redhat.com> To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Paolo Carlini Subject: Re: libstdc++/7186: DR179 for std::deque::iterator and const_iterator Reply-To: Paolo Carlini X-SW-Source: 2002-07/txt/msg00139.txt.bz2 List-Id: The following reply was made to PR libstdc++/7186; it has been noted by GNATS. From: Paolo Carlini To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, pcarlini@unitus.it, gcc-bugs@gcc.gnu.org, Benjamin Kosnik Cc: Subject: Re: libstdc++/7186: DR179 for std::deque::iterator and const_iterator Date: Wed, 03 Jul 2002 23:28:52 +0200 A little update on the existing practice (as requested by Benjamin): - Interestingly, Intel6 (Dinkumware) and Borland5.5.1 (Rogue Wave) show a behaviour identical to that of current mainline v3 that is 6642's testcase is compiled just fine, while 7186's testcase is not. - Metrowerks8 is able to compile both (this is the behaviour mandated by the resolution of DR179, according to my reading) Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7186