On 2017.08.29 at 15:22 +, Jason Mancini wrote:
> Been doing stability testing on my x86_64 Ryzen cpu using openSUSE's
> (Tumbleweed) "gcc7.1.1 20170802" + compiling Linux kernel source.
> Every so often, the build curiously stalls on a futex between cc1 and
> as. cc1 is on the futex. as is wa
Been doing stability testing on my x86_64 Ryzen cpu using openSUSE's
(Tumbleweed) "gcc7.1.1 20170802" + compiling Linux kernel source. Every so
often, the build curiously stalls on a futex between cc1 and as. cc1 is on the
futex. as is waiting to read. Could that hang be related to what's be
On 08/29/2017 12:55 PM, Markus Trippelsdorf wrote:
> On 2017.08.29 at 12:53 +0200, Martin Liška wrote:
>> On 08/29/2017 12:47 PM, Markus Trippelsdorf wrote:
>>> On 2017.08.29 at 12:42 +0200, Martin Liška wrote:
On 08/29/2017 12:39 PM, Martin Liška wrote:
> (gdb) bt
> #0 0x3fff950e
On 2017.08.29 at 12:53 +0200, Martin Liška wrote:
> On 08/29/2017 12:47 PM, Markus Trippelsdorf wrote:
> > On 2017.08.29 at 12:42 +0200, Martin Liška wrote:
> >> On 08/29/2017 12:39 PM, Martin Liška wrote:
> >>> (gdb) bt
> >>> #0 0x3fff950e58e4 in syscall () from /lib64/libc.so.6
> >>> #1 0x0
On 08/29/2017 12:47 PM, Markus Trippelsdorf wrote:
> On 2017.08.29 at 12:42 +0200, Martin Liška wrote:
>> On 08/29/2017 12:39 PM, Martin Liška wrote:
>>> (gdb) bt
>>> #0 0x3fff950e58e4 in syscall () from /lib64/libc.so.6
>>> #1 0x3fff94dbbdc4 in __cxxabiv1::__cxa_guard_acquire (g=0x3fff94
On 2017.08.29 at 12:42 +0200, Martin Liška wrote:
> On 08/29/2017 12:39 PM, Martin Liška wrote:
> > (gdb) bt
> > #0 0x3fff950e58e4 in syscall () from /lib64/libc.so.6
> > #1 0x3fff94dbbdc4 in __cxxabiv1::__cxa_guard_acquire (g=0x3fff94f26d40
> > > namespace)::__future_category_instance(
On 08/29/2017 12:39 PM, Martin Liška wrote:
> (gdb) bt
> #0 0x3fff950e58e4 in syscall () from /lib64/libc.so.6
> #1 0x3fff94dbbdc4 in __cxxabiv1::__cxa_guard_acquire (g=0x3fff94f26d40
> namespace)::__future_category_instance()::__fec>) at
> ../../../../libstdc++-v3/libsupc++/guard.cc:3
On 08/29/2017 11:15 AM, Stefan Ring wrote:
> On Tue, Aug 29, 2017 at 9:32 AM, Martin Liška wrote:
>> On 08/28/2017 09:15 PM, Martin Liška wrote:
>>> On 08/28/2017 04:06 PM, Jeff Law wrote:
On 08/28/2017 01:16 AM, Martin Liška wrote:
> Hello.
>
> I've just repeatedly seen stuck in
On Tue, Aug 29, 2017 at 9:32 AM, Martin Liška wrote:
> On 08/28/2017 09:15 PM, Martin Liška wrote:
>> On 08/28/2017 04:06 PM, Jeff Law wrote:
>>> On 08/28/2017 01:16 AM, Martin Liška wrote:
Hello.
I've just repeatedly seen stuck in build process:
make[5]: Entering director
On 08/28/2017 09:15 PM, Martin Liška wrote:
> On 08/28/2017 04:06 PM, Jeff Law wrote:
>> On 08/28/2017 01:16 AM, Martin Liška wrote:
>>> Hello.
>>>
>>> I've just repeatedly seen stuck in build process:
>>>
>>> make[5]: Entering directory
>>> `/home/marxin/Programming/gcc/objdir/powerpc64le-unknown
On 08/28/2017 04:06 PM, Jeff Law wrote:
On 08/28/2017 01:16 AM, Martin Liška wrote:
Hello.
I've just repeatedly seen stuck in build process:
make[5]: Entering directory
`/home/marxin/Programming/gcc/objdir/powerpc64le-unknown-linux-gnu/libstdc++-v3/po'
msgfmt -o de.mo ../../../../libstdc++-v3
On 08/28/2017 02:16 AM, Martin Liška wrote:
Hello.
I've just repeatedly seen stuck in build process:
make[5]: Entering directory
`/home/marxin/Programming/gcc/objdir/powerpc64le-unknown-linux-gnu/libstdc++-v3/po'
msgfmt -o de.mo ../../../../libstdc++-v3/po/de.po
49__asm volatile ("sc;
On 08/28/2017 01:16 AM, Martin Liška wrote:
> Hello.
>
> I've just repeatedly seen stuck in build process:
>
> make[5]: Entering directory
> `/home/marxin/Programming/gcc/objdir/powerpc64le-unknown-linux-gnu/libstdc++-v3/po'
> msgfmt -o de.mo ../../../../libstdc++-v3/po/de.po
>
> 49__as
13 matches
Mail list logo