[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-09-07 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

--- Comment #38 from Martin Liška  ---
So downloading the package and testing that with problematic 6.3 does not
reproduce. Can you please verify you have really GCC 6.4? If so, would it be
possible to create a virtual machine or a Docker image which I can replay and
thus reproduce?

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-09-06 Thread dilfridge at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

--- Comment #37 from Andreas K. Huettel  ---
Created attachment 42140
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42140=edit
gparted build log

Here's the build log from my Gentoo colleague.

If you need more, please tell me precisely what - I dont have that much
experience reporting here yet. Can't reopen the bug either.

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-09-01 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

--- Comment #36 from Martin Liška  ---
Please provide one more test-case that still fails and I will take a look. Feel
free to reopen it.

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-08-31 Thread dilfridge at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

--- Comment #35 from Andreas K. Huettel  ---
Oops sorry, that should have been:

According to https://bugs.gentoo.org/show_bug.cgi?id=629342 *not* fixed for
gcc-6.

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-08-31 Thread dilfridge at gentoo dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

Andreas K. Huettel  changed:

   What|Removed |Added

 CC||dilfridge at gentoo dot org

--- Comment #34 from Andreas K. Huettel  ---
According to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953 *not* fixed for
gcc-6.

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-06-22 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

Martin Liška  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #33 from Martin Liška  ---
Fixed on GCC 6.x, no plan to backport back to GCC 5, closing as resolved.

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-06-22 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

--- Comment #32 from Martin Liška  ---
Author: marxin
Date: Thu Jun 22 11:16:16 2017
New Revision: 249514

URL: https://gcc.gnu.org/viewcvs?rev=249514=gcc=rev
Log:
Backport r246899

2017-06-22  Martin Liska  

Backport from mainline
2017-04-12  Jan Hubicka  

PR lto/69953
* ipa-visibility.c (non_local_p): Fix typos.
(localize_node): When localizing symbol in same comdat group,
dissolve the group only when we know external symbols are going
to be privatized.
(function_and_variable_visibility): Do not localize DECL_EXTERNAL.

Modified:
branches/gcc-6-branch/gcc/ChangeLog
branches/gcc-6-branch/gcc/ipa-visibility.c

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-06-01 Thread db0451 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

--- Comment #31 from DB  ---
Uh, sorry. I mean when compiling my own application against glibmm and gtkmm,
using LTO on my app (only).

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-06-01 Thread db0451 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

DB  changed:

   What|Removed |Added

 CC||db0451 at gmail dot com

--- Comment #30 from DB  ---
I get similar issues when compiling glibmm-2.4 from git with g++ 6.3 and LTO,
but not without LTO: undefined references to destructors for
Glib::RefPtr and Glib::RefPtr.

Can this be related, or should I open another bug?

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2017-04-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

Jakub Jelinek  changed:

   What|Removed |Added

Summary|[5/6/7 Regression] Using|[5/6 Regression] Using lto
   |lto causes gtkmm/gparted|causes gtkmm/gparted and
   |and gtkmm/inkscape compile  |gtkmm/inkscape compile to
   |to fail |fail

--- Comment #29 from Jakub Jelinek  ---
Fixed on the trunk so far, thanks Honza.

[Bug c++/69953] [5/6 Regression] Using lto causes gtkmm/gparted and gtkmm/inkscape compile to fail

2016-03-23 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69953

Richard Biener  changed:

   What|Removed |Added

   Keywords||lto, wrong-code
   Priority|P3  |P2
 CC||jason at gcc dot gnu.org
  Component|lto |c++

--- Comment #20 from Richard Biener  ---
FE issue manifesting as wrong-code with LTO.