[Bug c/57483] New: Linux kernel (lto-3.9 branch) compilation fails with enabled LTO

[Bug c/57483] New: Linux kernel (lto-3.9 branch) compilation fails with enabled LTO

[marxin.liska at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57483

            Bug ID: 57483
           Summary: Linux kernel (lto-3.9 branch) compilation fails with
                    enabled LTO
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin.liska at gmail dot com

Andi Kleen is maintaining Linux kernel LTO branch:
https://github.com/andikleen/linux-misc

Repository version:
5c1e0bc49249c3ff44849a8f72e6cccd1486f38f

GCC used to be able to compile such kernel, regression was introduced in
revision: 198741

Error:
In function ‘alloc_iommu’:
lto1: internal compiler error: in input_gimple_stmt, at
gimple-streamer-in.c:287
0xc76db5 input_gimple_stmt
    ../../gcc/gimple-streamer-in.c:286
0xc76db5 input_bb(lto_input_block*, LTO_tags, data_in*, function*, int)
    ../../gcc/gimple-streamer-in.c:345
0x77d1b3 input_function
    ../../gcc/lto-streamer-in.c:887
0x77d1b3 lto_read_body
    ../../gcc/lto-streamer-in.c:1011
0x77d1b3 lto_input_function_body(lto_file_decl_data*, tree_node*, char const*)
    ../../gcc/lto-streamer-in.c:1055
0x4ff322 lto_materialize_function
    ../../gcc/lto/lto.c:226
0x4ff322 materialize_cgraph
    ../../gcc/lto/lto.c:3084
0x506a88 lto_main()
    ../../gcc/lto/lto.c:3348
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[1]: *** [/tmp/ccRWZATW.ltrans8.ltrans.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/tmp/cckatHC0.s: Assembler messages:
/tmp/cckatHC0.s:10068: Error: symbol `__compound_literal.0' is already defined
/tmp/cckatHC0.s:30211: Error: symbol `__compound_literal.0' is already defined
make[1]: *** [/tmp/ccRWZATW.ltrans6.ltrans.o] Error 1
lto-wrapper: make returned 2 exit status
/home/marxin/gcc-jan/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/ld: lto-wrapper
failed
collect2: error: ld returned 1 exit status
make: *** [vmlinux] Error 1
>From gcc-bugs-return-423585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 31 13:06:00 2013
Return-Path: <gcc-bugs-return-423585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24595 invoked by alias); 31 May 2013 13:05:59 -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 24496 invoked by uid 48); 31 May 2013 13:05:49 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57319] [4.8 Regression]: bogus "defaulted move assignment for ... calls a non-trivial move assignment operator for virtual base ..."
Date: Fri, 31 May 2013 13:05: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work resolution cf_known_to_fail
Message-ID: <bug-57319-4-RhQLtWKtIk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57319-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57319-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: 2013-05/txt/msg02258.txt.bz2
Content-length: 541

http://gcc.gnu.org/bugzilla/show_bug.cgi?idW319

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
      Known to work|                            |4.8.2
         Resolution|---                         |FIXED
      Known to fail|                            |4.8.1

--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 4.8.2.

[Bug lto/57483] Linux kernel (lto-3.9 branch) compilation fails with enabled LTO

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57483

Bug 57483 depends on bug 57334, which changed state.

Bug 57334 Summary: [4.9 regression] ICE: in input_gimple_stmt, at gimple-streamer-in.c:287
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57334

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

[Bug lto/57483] Linux kernel (lto-3.9 branch) compilation fails with enabled LTO

[marxin.liska at gmail dot com]

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57483

--- Comment #2 from Martin Liška <marxin.liska at gmail dot com> ---
Works for me, could be marker as fixed.
>From gcc-bugs-return-424604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 19 00:41:53 2013
Return-Path: <gcc-bugs-return-424604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29295 invoked by alias); 19 Jun 2013 00:41:53 -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 29248 invoked by uid 48); 19 Jun 2013 00:41:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/54562] mutex and condition variable timers
Date: Wed, 19 Jun 2013 00:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.7.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-54562-4-UdMOP7AMwi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54562-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54562-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: 2013-06/txt/msg00983.txt.bz2
Content-length: 2116

http://gcc.gnu.org/bugzilla/show_bug.cgi?idT562

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |redi at gcc dot gnu.org

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Created attachment 30320
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id0320&actioníit
proposed patch to use clocks correctly

The <condition_variable> change should be unnecessary, as high_resolution_clock
is a typedef for system_clock in our implementation.

The timed_mutex change is an improvement but not ideal, because the standard
says implementations "should" use a steady clock for try_lock_for() but use the
system_clock for try_lock_until(), and pthread_mutex_timedlock() uses
CLOCK_REALTIME, which corresponds to our system_clock.

I'm going to test this patch (against the current svn trunk, after
gcc.gnu.org/r200180) to fix the timed_mutex issue. The patch attempts to use
the steady clock for relative timeouts, converting to the high_resolution_clock
(aka system_clock) for the pthread call, and re-checks on timeout to handle
cases where a clock is adjusted during the wait.

N.B. your test technically has undefined behaviour because it attempts to
relock the mutex in the same thread, I'm using this to reproduce the problem
instead:

#include <iostream>
#include <chrono>
#include <mutex>
#include <thread>

typedef std::chrono::high_resolution_clock rt_clock;
typedef std::chrono::time_point<rt_clock> rt_time_point;

std::timed_mutex mutex;

void f()
{
    mutex.try_lock_for(std::chrono::seconds(3));
}

int main()
{
    mutex.lock();
    std::cout << "mutex locked" << std::endl;

    rt_time_point t1 = rt_clock::now();
    std::thread(f).join();
    rt_time_point t2 = rt_clock::now();
    std::cout << "delay: "
              <<
std::chrono::duration_cast<std::chrono::seconds>(t2-t1).count()
              << std::endl;
    return 0;
}

[Bug lto/57483] Linux kernel (lto-3.9 branch) compilation fails with enabled LTO

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57483

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Andi also reported success.