From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16156 invoked by alias); 22 Feb 2015 05:18:57 -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 15799 invoked by uid 48); 22 Feb 2015 05:17:51 -0000 From: "potswa at mac dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65159] New: Linker forgets definition of type_info::__is_pointer_p Date: Sun, 22 Feb 2015 07:19: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: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: potswa at mac dot com X-Bugzilla-Status: UNCONFIRMED 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 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-02/txt/msg02409.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D65159 Bug ID: 65159 Summary: Linker forgets definition of type_info::__is_pointer_p Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: potswa at mac dot com In r220825 on Darwin/x64, the build fails with a complaint that type_info::__is_pointer_p is undefined, although it's still there in libstdc++-v3/libsupc++/tinfo.cc as ever. If I go to that file and comment out __is_function_p, it complains about th= at function instead and not __is_pointer_p. If I swap the order of those two definitions, the complaint goes away and the build succeeds. (Hmm, I might = have the functions backwards=E2=80=A6 same difference anyway.) The problem persists if I update to the current trunk, so this isn't comple= tely transient. >>From gcc-bugs-return-478078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 22 05:20:08 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17215 invoked by alias); 22 Feb 2015 05:20:06 -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 17143 invoked by uid 48); 22 Feb 2015 05:20:00 -0000 From: "potswa at mac dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65160] New: Linker forgets definition of type_info::__is_pointer_p Date: Sun, 22 Feb 2015 08:09: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: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: potswa at mac dot com X-Bugzilla-Status: UNCONFIRMED 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 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-02/txt/msg02410.txt.bz2 Content-length: 965 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D65160 Bug ID: 65160 Summary: Linker forgets definition of type_info::__is_pointer_p Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: potswa at mac dot com In r220825 on Darwin/x64, the build fails with a complaint that type_info::__is_pointer_p is undefined, although it's still there in libstdc++-v3/libsupc++/tinfo.cc as ever. If I go to that file and comment out __is_function_p, it complains about th= at function instead and not __is_pointer_p. If I swap the order of those two definitions, the complaint goes away and the build succeeds. (Hmm, I might = have the functions backwards=E2=80=A6 same difference anyway.) The problem persists if I update to the current trunk, so this isn't comple= tely transient. >>From gcc-bugs-return-478079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 22 07:19:51 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29034 invoked by alias); 22 Feb 2015 07:19:50 -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 28987 invoked by uid 48); 22 Feb 2015 07:19:45 -0000 From: "kkojima at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65153] [SH][4.9 Regression] "insn does not satisfy its constraints" when compiling libmcrypt Date: Sun, 22 Feb 2015 08:34: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: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kkojima at gcc dot gnu.org X-Bugzilla-Status: NEW 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: attachments.isobsolete attachments.created 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-02/txt/msg02411.txt.bz2 Content-length: 575 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65153 Kazumoto Kojima changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #34831|0 |1 is obsolete| | --- Comment #7 from Kazumoto Kojima --- Created attachment 34832 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34832&action=edit a possible patch (take 2) I've uploaded a wrong patch. Try again.