public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "timo.teras at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/64812] [4.9 regression] x86 LibreOffice Build failure: undefined reference to acquire
Date: Wed, 04 Feb 2015 09:33:00 -0000	[thread overview]
Message-ID: <bug-64812-4-LJBRCsSi9N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64812-4@http.gcc.gnu.org/bugzilla/>

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

Timo Teräs <timo.teras at iki dot fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |timo.teras at iki dot fi

--- Comment #3 from Timo Teräs <timo.teras at iki dot fi> ---
I can reproduce this, but unfortunately I don't have minimalistic test case
yet.

As a workaround removing -fvisibility-inlines-hidden from the build flags,
makes things work in the libreoffice.

What is involved / happening is:

The non-virtual thunks are in a DSO, but marked hidden. This is caused by
-fvisibility-inlines-hidden. The ::acquire members are virtual, but with inline
implementation (no inline marking / attribute though). The class itself is
marked __attribute__((visibility("default"))).

It appears that the places getting these unresolved symbols are trying to call
external symbol, even though it's inline implementation.

Apparently optimization flags, code context affects when this happens.

The symptoms sounds very much similar to what was in llvm:
http://llvm.org/bugs/show_bug.cgi?id=12255
>From gcc-bugs-return-475970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 04 09:35:29 2015
Return-Path: <gcc-bugs-return-475970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9548 invoked by alias); 4 Feb 2015 09:35:29 -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 9478 invoked by uid 48); 4 Feb 2015 09:35:23 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64932] [4.9/5.0 Regression] ICE in gfc_conv_descriptor_data_get for generated finalizer
Date: Wed, 04 Feb 2015 09:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus 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: 4.9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-64932-4-vvmgziFkPa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64932-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/msg00303.txt.bz2
Content-length: 886

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.9.3
            Summary|[5.0] ICE on module end,    |[4.9/5.0 Regression] ICE in
                   |gfc_conv_descriptor_data_ge |gfc_conv_descriptor_data_ge
                   |t                           |t for generated finalizer

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
The problem seems to occur in the finalizer, i.e. __final_coo_graphs_Coo_graph
for the component ref (ptr2 is of type coo_graph):

  ptr2->edges

which is an array_type - but with fixed bounds; it fails in
gfc_conv_descriptor_data_get for line

157       gcc_assert (GFC_DESCRIPTOR_TYPE_P (type));


  parent reply	other threads:[~2015-02-04  9:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  2:48 [Bug regression/64812] New: " lukebenes at hotmail dot com
2015-01-27  6:48 ` [Bug regression/64812] " trippels at gcc dot gnu.org
2015-01-27  6:56 ` trippels at gcc dot gnu.org
2015-01-27 11:11 ` rguenth at gcc dot gnu.org
2015-02-04  9:33 ` timo.teras at iki dot fi [this message]
2015-02-13 18:04 ` basile at opensource dot dyc.edu
2015-02-16 14:10 ` mstahl at redhat dot com
2015-02-16 14:14 ` mstahl at redhat dot com
2015-02-27  8:39 ` [Bug ipa/64812] " trippels at gcc dot gnu.org
2015-02-27 14:23 ` mstahl at redhat dot com
2015-02-27 14:48 ` trippels at gcc dot gnu.org
2015-06-26 20:18 ` jakub at gcc dot gnu.org
2015-06-26 20:39 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-64812-4-LJBRCsSi9N@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).