From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11932 invoked by alias); 19 Nov 2004 01:26:52 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11911 invoked from network); 19 Nov 2004 01:26:48 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org with SMTP; 19 Nov 2004 01:26:48 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id iAJ1XNqC026949 for ; Thu, 18 Nov 2004 17:33:23 -0800 (PST) Received: from relay3.apple.com (relay3.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.14) with ESMTP id ; Thu, 18 Nov 2004 17:27:26 -0800 Received: from [17.201.20.87] (mrs2.apple.com [17.201.20.87]) by relay3.apple.com (8.12.11/8.12.11) with ESMTP id iAJ1QjDU019449; Thu, 18 Nov 2004 17:26:45 -0800 (PST) In-Reply-To: <20041118102741.A8347@synopsys.com> References: <8AD5AEEF-3914-11D9-8BD2-000A95BCF344@apple.com> <78169FF3-3916-11D9-AEB4-000A95D692F4@physics.uc.edu> <4D2CF60C-3919-11D9-8BD2-000A95BCF344@apple.com> <20041117212847.A26376@synopsys.com> <6F5FC748-7BBD-44B9-8DDC-246949F16102@apple.com> <20041118102741.A8347@synopsys.com> Mime-Version: 1.0 (Apple Message framework v679) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <77E8D36A-C0C2-4B03-964C-BEE0FE7BBBC3@apple.com> Cc: Matt Austern , Andrew Pinski , gcc mailing list Content-Transfer-Encoding: 7bit From: Mike Stump Subject: Re: generalized lvalues Date: Fri, 19 Nov 2004 01:39:00 -0000 To: Joe Buck X-SW-Source: 2004-11/txt/msg00661.txt.bz2 On Nov 18, 2004, at 10:27 AM, Joe Buck wrote: > Really? AFAIK. > Can you show some of the example errors? Sounds boring and tedious, I don't see any benefit to doing that work. I've accepted the extension is gone and just plan on informing users it is gone. If details about that would help bring it back and someone around here really wants to bring it back, then, they can furnish those details... :-) > And are they really due to this extension specifically? AFAIK. The side world build people do the builds with newer compilers on the world, and then attempt to categorize the failures and the causes of those failures. We get ICEs out of it, tightened up compilers, codegen bugs (link failures, assembly failures) and so on. Usually the first in the series of bugs is routed through one of the compiler people to discern what category the propblem is in, and then farmed out as appropriate. If two independent things cause otherwise identical error messages, then, it is possible there could be multiple causes. In any event, what we do know, is that these things used to compile, and now don't. Also, this is a lower bound number, as there can be other reasons why the project didn't get far enough in the compilation to find such a problem.