iron_learn/target/debug/deps/libprofiling-139ae438dcac3df5.rlib

📄 libprofiling-139ae438dcac3df5.rlib
/home/palash/git/iron_learn/target/debug/deps/libprofiling-139ae438dcac3df5.rlib
Language: rlib • Lines: 193
!<arch>
/               0           0     0     0       8         `
//                                              68        `
profiling-139ae438dcac3df5.profiling.2d6d25b4bd04d11b-cgu.0.rcgu.o/
lib.rmeta/      0           0     0     644     5568      `
ELF>@@@GNU�rust
#rustc 1.92.0 (ded5c06cf 2025-12-08)��١�	�T�6a��D�
-5080178c80bf7a93�profiling_procmacros�e�9���H�A����
�-0d8c0e1df4c15e00��**�٭T��HО�9�-3e2e950d4bac10b5��puffin�4��<�profile-with-puffin�����puffin_impl�\��<������optick�4��<�profile-with-optick�����optick_impl�\��<������superluminal_perf����<�profile-with-superluminal�����%superluminal_impl����<��ܞ��%tracing�<��<�profile-with-tracing����� tracing_impl�d��<������ tracy_client�d��<�profile-with-tracy�����
tracy_impl�T��<������type_check_impl�|��<�
type-check�d����
empty_impl�scope�function_scope�register_thread�finish_frame��
all_functions�l�function�D��$��,��t�	�|�	�d�

����������������	�}
��#���Ԓ�t�T����  Opens a scope. Two variants:��!HE  - profiling::scope!(name: &str) - Opens a scope with the given name��ja^  - profiling::scope!(name: &str, data: &str) - Opens a scope with the given name and an extra���b_    datafield. Details of this depend on the API, but it should be a &str. If the extra data is���eb    named, it will be named "tag". Some APIs support adding more data (for example, `optic::tag!`)���<� ```��� profiling::scope!("outer");��� for _ in 0..10 {���EB     profiling::scope!("inner", format!("iteration {}").as_str());�,� }�<��
'|�e����,�8�
$�&�8�$�*���%���	,�8�
$�&�8�$�$�,�8data�$�&�8�$�*���%�����A> Opens a scope automatically named after the current function.���QN - profiling::function_scope!() - Opens a scope with the current function name���tq - profiling::function_scope!(data: &str) - Opens a scope with the current function name and an extra data field.���<��
�� fn function_a(){���%"     profiling::function_scope!();�,����" fn function_b(iteration: u32){���PM     profiling::function_scope!(format!("iteration {}", iteration).as_str());�,��<��
'|���	�	�	�	*�	�	�	%�	�	�	,�	8�$�	&�	8�$�	*�	�	�	%�	����	_\ Registers a thread with the profiler API(s). This is usually setting a name for the thread.���
 Two variants:���
[X  - register_thread!() - Tries to get the name of the thread, or an ID if no name is set���OL  - register_thread!(name: &str) - Registers the thread using the given name�'|������*���%���,�8�
$�&�8�$�*���%���
��a^ Finishes the frame. This isn't strictly necessary for some kinds of applications but a pretty���
#  normal thing to track in games.�'|�
�
�
�
�
*�
�
�
%�
T����%m-�Qo����L���r���:���葎��/S��.��m.�P��+]�n+����&^;��!�yK���{��[��i�ph�fI����Ml\ ���

�
��))))�?E
2
��������
�e
�����<B
/
�-9Ndw@F
3
"%����%m-��Z�`*��������ODHT �����&^;�����葎���Qo����L!�yK������%m-ph�fI��
m.�P�/S��.��{��[��i�	��Ml\ ����r���:�+]�n+�Ta&x�^�x�}F�UTa&x�^�x�}F�U]/home/palash/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/profiling-1.0.17/src/lib.rs� ���hσ�6|U>4;�{��b;aQ % 
&
.% 
&
-`N(6 % 
&
.% 
&
$((((((...)))'''%%+&$%%+&$��>�$6+o��U�d/home/palash/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/profiling-1.0.17/src/empty_impl.rs� w>�C(1�Ѹ���Ǆk��
4!Ibcf F$BRu&#Q`\Pb$fK�����RիV��7x86_64-unknown-linux-gnu�w�\�+�[/�� "�?�	profiling�-139ae438dcac3df5����%m-�#��`!N�rust-end-file.note.gnu.property.shstrtab.strtab.symtab.rmeta@ .�`�&�	5/0              0           0     0     644     632       `
ELF>�@@rustc version 1.92.0 (ded5c06cf 2025-12-08)0��.text.comment.note.GNU-stack.strtab.symtabprofiling.2d6d25b4bd04d11b-cgu.0 �Q@0@-m(p0