search for: 104021

...nly faster at codegen than local with such bitcode files. Let me know if the link doesn't work: https://spreadsheets.google.com/a/google.com/ccc?key=0At5EJFcCBf-wdDgtd2FoZjU4bFBzcFBtT25rQkgzMEE&hl=en Misc stuff: I ran into an "UNREACHABLE executed" using linear scan on revision 104021, so I used an older version for that. 0 llc.hg 0x0000000000af4d7f 1 llc.hg 0x0000000000af54fa 2 libpthread.so.0 0x00007fb1734b67d0 3 libc.so.6 0x00007fb1725d2095 gsignal + 53 4 libc.so.6 0x00007fb1725d3af0 abort + 272 5 llc.hg 0x0000000000ad4932 llvm::l...

...itcode files. Let me know if the link doesn't work: > > https://spreadsheets.google.com/a/google.com/ccc?key=0At5EJFcCBf-wdDgtd2FoZjU4bFBzcFBtT25rQkgzMEE&hl=en Sorry, can't read that. > Misc stuff: I ran into an "UNREACHABLE executed" using linear scan on revision 104021, so I used an older version for that. Please use bugpoint to reduce the test case and then submit a PR. bugpoint -run-llc 403.gcc.linked.bc -tool-args -asm-verbose=false -O0 Thanks, /jakob

On May 17, 2010, at 9:09 PM, Rafael Espindola wrote: >> The fast and local register allocators are meant to be used on unoptimized code, a 'Debug build'. While they do work on optimized code, they do not give good results. Their primary goal is compile time, not code quality. > > Yes, we have a somewhat uncommon use case. It is fine to spend time > optimizing bitcode (LTO

> The fast and local register allocators are meant to be used on unoptimized code, a 'Debug build'. While they do work on optimized code, they do not give good results. Their primary goal is compile time, not code quality. Yes, we have a somewhat uncommon use case. It is fine to spend time optimizing bitcode (LTO is a OK), but we want to make the final IL -> Executable translation

In glfsheal-Connection.log I see many lines like: [2023-03-13 23:04:40.241481 +0000] E [MSGID: 104021] [glfs-mgmt.c:586:glfs_mgmt_getspec_cbk] 0-gfapi: failed to get the volume file [{from server}, {errno=2}, {error=File o directory non esistente}] And *lots* of gfid-mismatch errors in glustershd.log . Couldn't find anything that would prevent heal to start. :( Diego Il 21/03/2023 20:39,...

...lume file contents?Maybe it really can't find (or access) a specific volfile ? Best Regards,Strahil Nikolov? On Fri, Mar 24, 2023 at 8:07, Diego Zuccato<diego.zuccato at unibo.it> wrote: In glfsheal-Connection.log I see many lines like: [2023-03-13 23:04:40.241481 +0000] E [MSGID: 104021] [glfs-mgmt.c:586:glfs_mgmt_getspec_cbk] 0-gfapi: failed to get the volume file [{from server}, {errno=2}, {error=File o directory non esistente}] And *lots* of gfid-mismatch errors in glustershd.log . Couldn't find anything that would prevent heal to start. :( Diego Il 21/03/2023 20:39,...

...or access) a specific volfile ? > > Best Regards, > Strahil Nikolov > > On Fri, Mar 24, 2023 at 8:07, Diego Zuccato > <diego.zuccato at unibo.it> wrote: > In glfsheal-Connection.log I see many lines like: > [2023-03-13 23:04:40.241481 +0000] E [MSGID: 104021] > [glfs-mgmt.c:586:glfs_mgmt_getspec_cbk] 0-gfapi: failed to get the > volume file [{from server}, {errno=2}, {error=File o directory non > esistente}] > > And *lots* of gfid-mismatch errors in glustershd.log . > > Couldn't find anything that would pr...

I have no clue. Have you checked for errors in the logs ? Maybe you might find something useful. Best Regards,Strahil Nikolov? On Tue, Mar 21, 2023 at 9:56, Diego Zuccato<diego.zuccato at unibo.it> wrote: Killed glfsheal, after a day there were 218 processes, then they got killed by OOM during the weekend. Now there are no processes active. Trying to run "heal info" reports

...> > >? ? On Fri, Mar 24, 2023 at 8:07, Diego Zuccato > >? ? <diego.zuccato at unibo.it <mailto:diego.zuccato at unibo.it>> wrote: > >? ? In glfsheal-Connection.log I see many lines like: > >? ? [2023-03-13 23:04:40.241481 +0000] E [MSGID: 104021] > >? ? [glfs-mgmt.c:586:glfs_mgmt_getspec_cbk] 0-gfapi: failed to get the > >? ? volume file [{from server}, {errno=2}, {error=File o directory non > >? ? esistente}] > > > >? ? And *lots* of gfid-mismatch errors in glustershd.log . >...