sync with cpython 83cb89b9

Author: github-actions[bot]

Diff for: howto/perf_profiling.po

@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.13\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-03-29 00:14+0000\n"
+"POT-Creation-Date: 2025-04-19 00:14+0000\n"
 "PO-Revision-Date: 2023-12-09 17:39+0800\n"
 "Last-Translator: Matt Wang <[email protected]>\n"
 "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
@@ -578,13 +578,55 @@ msgstr ""
 
 #: ../../howto/perf_profiling.rst:257
 msgid ""
-"Notice that when using ``--call-graph dwarf`` the ``perf`` tool will take "
-"snapshots of the stack of the process being profiled and save the "
-"information in the ``perf.data`` file. By default the size of the stack dump "
-"is 8192 bytes but the user can change the size by passing the size after "
-"comma like ``--call-graph dwarf,4096``. The size of the stack dump is "
-"important because if the size is too small ``perf`` will not be able to "
-"unwind the stack and the output will be incomplete. On the other hand, if "
-"the size is too big, then ``perf`` won't be able to sample the process as "
-"frequently as it would like as the overhead will be higher."
+"When using ``--call-graph dwarf``, the ``perf`` tool will take snapshots of "
+"the stack of the process being profiled and save the information in the "
+"``perf.data`` file. By default, the size of the stack dump is 8192 bytes, "
+"but you can change the size by passing it after a comma like ``--call-graph "
+"dwarf,16384``."
+msgstr ""
+
+#: ../../howto/perf_profiling.rst:263
+msgid ""
+"The size of the stack dump is important because if the size is too small "
+"``perf`` will not be able to unwind the stack and the output will be "
+"incomplete. On the other hand, if the size is too big, then ``perf`` won't "
+"be able to sample the process as frequently as it would like as the overhead "
+"will be higher."
+msgstr ""
+
+#: ../../howto/perf_profiling.rst:269
+msgid ""
+"The stack size is particularly important when profiling Python code compiled "
+"with low optimization levels (like ``-O0``), as these builds tend to have "
+"larger stack frames. If you are compiling Python with ``-O0`` and not seeing "
+"Python functions in your profiling output, try increasing the stack dump "
+"size to 65528 bytes (the maximum)::"
+msgstr ""
+
+#: ../../howto/perf_profiling.rst:275
+#, fuzzy
+msgid ""
+"$ perf record -F 9999 -g -k 1 --call-graph dwarf,65528 -o perf.data python -"
+"Xperf_jit my_script.py"
+msgstr "$ perf record -F 9999 -g -o perf.data python my_script.py"
+
+#: ../../howto/perf_profiling.rst:277
+msgid "Different compilation flags can significantly impact stack sizes:"
+msgstr ""
+
+#: ../../howto/perf_profiling.rst:279
+msgid ""
+"Builds with ``-O0`` typically have much larger stack frames than those with "
+"``-O1`` or higher"
+msgstr ""
+
+#: ../../howto/perf_profiling.rst:280
+msgid ""
+"Adding optimizations (``-O1``, ``-O2``, etc.) typically reduces stack size"
+msgstr ""
+
+#: ../../howto/perf_profiling.rst:281
+msgid ""
+"Frame pointers (``-fno-omit-frame-pointer``) generally provide more reliable "
+"stack unwinding"
 msgstr ""