Displaying 3 results from an estimated 3 matches for "27510".
Did you mean:
27501
2014 Jul 25
1
2.2.13 + hg: Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (fd >= 0)
.../usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2d)
[0xb9842d] -> dovecot/pop3(main+0x2a9) [0x804b3b9] ->
/lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x6f7dec] ->
dovecot/pop3 [0x804aeb1]
Jul 25 14:12:38 dovecot: pop3(cen at so.red): Fatal: master: service(pop3):
child 27510 killed with signal 6 (core dumped)
(gdb) bt
#0 0x00b1a402 in __kernel_vsyscall ()
#1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6
#2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6
#3 0x00bdfc14 in default_fatal_finish (type=<value optimized out>,
status=0) at failu...
2016 Mar 24
0
[RFC] Lazy-loading of debug info metadata
...accurate? If so, I don't see remaining benefit in delaying the
global metadata parsing, just an extra code path to maintain. Do you
agree?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: function-local-metadata-v1.patch
Type: application/octet-stream
Size: 27510 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160323/0b19393f/attachment-0001.obj>
2016 Mar 23
7
[RFC] Lazy-loading of debug info metadata
I have some ideas to allow the BitcodeReader to lazy-load debug info
metadata, and wanted to air this on llvm-dev before getting too deep
into the code.
Motivation
==========
Based on some analysis Mehdi ran (ping him for details), there are three
(related) compile-time bottlenecks we're seeing with `-flto=thin -g`:
a) Reading the large number of Metadata bitcode records in the global