[Bug c++/65159] New: Linker forgets definition of type_info::__is_pointer_p

[Bug c++/65159] New: Linker forgets definition of type_info::__is_pointer_p

[potswa at mac dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 6126 bytes --]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

            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 that
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… same difference anyway.)

The problem persists if I update to the current trunk, so this isn't completely
transient.
>From gcc-bugs-return-478078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 22 05:20:08 2015
Return-Path: <gcc-bugs-return-478078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
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: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
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" <gcc-bugzilla@gcc.gnu.org>
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: <bug-65160-4@http.gcc.gnu.org/bugzilla/>
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=65160

            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 that
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… same difference anyway.)

The problem persists if I update to the current trunk, so this isn't completely
transient.
>From gcc-bugs-return-478079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 22 07:19:51 2015
Return-Path: <gcc-bugs-return-478079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
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: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
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" <gcc-bugzilla@gcc.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: <bug-65153-4-bXU8Btx2PN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65153-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65153-4@http.gcc.gnu.org/bugzilla/>
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?ide153

Kazumoto Kojima <kkojima at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #34831|0                           |1
        is obsolete|                            |

--- Comment #7 from Kazumoto Kojima <kkojima at gcc dot gnu.org> ---
Created attachment 34832
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id4832&actioníit
a possible patch (take 2)

I've uploaded a wrong patch.  Try again.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[schwab@linux-m68k.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
*** Bug 65160 has been marked as a duplicate of this bug. ***

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-apple-darwin*

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Other people are building OK on Darwin so you'll need to give more info.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Other people are building OK on Darwin so you'll need to give more info.

I don't see that at r221188. What is needed to reproduce it?

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Dunno, I just logged into a darwin14 box and tried to build. I'm trying again
with a clean build now.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
A clean non-bootstrap build completed OK. Running a clean bootstrap now.

David, are you seeing this for a completely clean build?

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|jwakely.gcc at gmail dot com       |

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I don't see this for a clean bootstrap either. I only saw it when running
'make' in an existing build tree after updating to the latest trunk.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[potswa at mac dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #8 from David Krauss <potswa at mac dot com> ---
It was an updated tree. I'm not sure what revision it was updated from, but it
was probably late January.

Sorry for the delay, my machine got completely hosed by a bad RAM chip. Took
the filesystem with it. So, bit rot and disk corruption can't be ruled out
either.

Jonathan, what does the "confirmed" mean, were you able to reproduce it at all?

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Krauss from comment #8)
> Jonathan, what does the "confirmed" mean, were you able to reproduce it at
> all?

Yes, but not after starting a fresh build in am empty directory, so it seems to
be due to building in a dirty tree.

Please try again with a clean build.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[potswa at mac dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #10 from David Krauss <potswa at mac dot com> ---
I made a clean build of r220825, and it succeeded. Then I downgraded to
r220000, and it produced similar link errors, although not in type_info.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Krauss from comment #10)
> I made a clean build of r220825, and it succeeded. Then I downgraded to
> r220000, and it produced similar link errors, although not in type_info.

This is rather vague, did you do a clean build of r220000?

If not, there's nothing we need to fix here, it's user error.

[Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p

[potswa at mac dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65159

--- Comment #12 from David Krauss <potswa at mac dot com> ---
I did exactly the steps that I mentioned: cleanly build r220825, update to
r220000, and build again without cleaning first. The object being to roughly
replicate the conditions when the bug was originally observed — except
originally the update was in the other direction, r220000-ish to r220825.

Is it always an error to do a non-clean build? The problem seems to happen
pretty regularly.
>From gcc-bugs-return-480497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 16 23:57:05 2015
Return-Path: <gcc-bugs-return-480497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51093 invoked by alias); 16 Mar 2015 23:57:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51072 invoked by uid 48); 16 Mar 2015 23:57:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65159] Linker forgets definition of type_info::__is_pointer_p
Date: Mon, 16 Mar 2015 23:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
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: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
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 resolution
Message-ID: <bug-65159-4-X3r0tHNb9f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65159-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65159-4@http.gcc.gnu.org/bugzilla/>
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-03/txt/msg01641.txt.bz2
Content-length: 1020

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide159

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |INVALID

--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Krauss from comment #12)
> Is it always an error to do a non-clean build?

If it works without doing a clean build then fine, you're in luck, but it's not
supported and there are absolutely not guarantees that it will work. So please
don't report bugs that you can't reproduce after a clean build, *especially*
bootstrap and build-related failures.

If you configure with --enable-maintainer-mode then the makefiles contain some
additional dependencies that might make partial rebuilds work more reliably,
but you should still do a clean build before reporting any build failures.