Displaying 4 results from an estimated 4 matches for "4685743".
2013 Feb 06
2
[LLVMdev] LLVM Coverage GCDA Flush API
..., since
the flush functions are registered with atexit(). This is the bug report:
http://llvm.org/bugs/show_bug.cgi?id=12144
I have what I think is a basic implementation of the `__gcov_flush` call,
although I called this version `__llvm_gcov_flush`. Here is the diff
https://gist.github.com/ashgti/4685743 if anyone would like to see it.
So, my question is where should I go from here? Do I need to email the
exact patch to llvm-commits? This touches both the llvm and compiler-rt, so
I don't know if that changes anything.
Thanks,
--
John Harrison
-------------- next part --------------
An HTML...
2013 Feb 06
0
[LLVMdev] LLVM Coverage GCDA Flush API
...e flush functions are registered with atexit(). This is the bug report: http://llvm.org/bugs/show_bug.cgi?id=12144
>
> I have what I think is a basic implementation of the `__gcov_flush` call, although I called this version `__llvm_gcov_flush`. Here is the diff https://gist.github.com/ashgti/4685743 if anyone would like to see it.
>
> So, my question is where should I go from here? Do I need to email the exact patch to llvm-commits? This touches both the llvm and compiler-rt, so I don't know if that changes anything.
>
>
> Thanks,
>
> --
> John Harrison
> _...
2013 Feb 06
2
[LLVMdev] LLVM Coverage GCDA Flush API
...ons are registered with atexit(). This is the bug
> report: http://llvm.org/bugs/show_bug.cgi?id=12144
>
> I have what I think is a basic implementation of the `__gcov_flush` call,
> although I called this version `__llvm_gcov_flush`. Here is the diff
> https://gist.github.com/ashgti/4685743 if anyone would like to see it.
>
> So, my question is where should I go from here? Do I need to email the
> exact patch to llvm-commits? This touches both the llvm and compiler-rt, so
> I don't know if that changes anything.
>
>
> Thanks,
>
> --
> John Harrison
&g...
2008 Dec 21
2
corruption happening sometimes when I do a shutdown -r now
...forced.
Pass 1: Checking inodes, blocks, and sizes
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 90119: 4685733 4685734 4685735
4685736 4685737 4685738 4685739 4685740 4685741 4685742 4685743
4685744 4685745 4685750 4685751 4685752 4685753 4127735 4127736
4127737 4127738 4688088 4688089 4688090 4688091 4688092 4688093
4688094 4688095 4688096 4688097 4688066 4688067 4688068 4688069
4688070 4688071 4688072 4688073 4688074 4688075 4688076 4688077
4688078 4688079 4688080 4688081 4688415 468...