From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79559 invoked by alias); 15 May 2015 14:32:51 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 79464 invoked by uid 48); 15 May 2015 14:32:43 -0000 From: "tromey at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66161] New: gcc silent about type incompleteness in error message Date: Fri, 15 May 2015 14:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-05/txt/msg01180.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66161 Bug ID: 66161 Summary: gcc silent about type incompleteness in error message Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: tromey at gcc dot gnu.org Target Milestone: --- This source is distilled from a more complicated real-world case that arose in https://bugzilla.mozilla.org/show_bug.cgi?id=3D1165184 class Base { }; class Incomplete; // : public Base template Base* blah_cast(T *arg) { return arg; } Base* function(Incomplete *arg) { return blah_cast(arg); } Compiling this yields: pokyo. g++ -c s.cc s.cc: In instantiation of =E2=80=98Base* blah_cast(T*) [with T =3D Incomple= te]=E2=80=99: s.cc:10:23: required from here s.cc:6:34: error: cannot convert =E2=80=98Incomplete*=E2=80=99 to =E2=80=98= Base*=E2=80=99 in return Base* blah_cast(T *arg) { return arg; } ^ In this case it is obvious that Incomplete is an incomplete type. However, in the real-world code this is far from obvious. I think it would be handy if gcc printed something like "note: type 'Incomplete' is incomplete at this point; missing include?". >>From gcc-bugs-return-486339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 15 14:32:13 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 77685 invoked by alias); 15 May 2015 14:32:13 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 77637 invoked by uid 48); 15 May 2015 14:32:08 -0000 From: "rearnsha at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66136] AArch64 geniterators.sh relies on GNU sed syntax, causing build failure on FreeBSD and probably Mac Date: Fri, 15 May 2015 14:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rearnsha at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-05/txt/msg01179.txt.bz2 Content-length: 796 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66136 Richard Earnshaw changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-05-15 Ever confirmed|0 |1 --- Comment #4 from Richard Earnshaw --- According to: http://pubs.opengroup.org/onlinepubs/009695399/utilities/sed.html [In a replacement] the meaning of a '\' immediately followed by any character other than '&', '\', a digit, or the delimiter character used for this command, is unspecified. So I think that rules out all the normal escaped characters.