You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ideas.html
+2-2
Original file line number
Diff line number
Diff line change
@@ -685,9 +685,9 @@ <h2>
685
685
<br/>
686
686
Task outline:<br/>
687
687
<ul>
688
-
<li>There's already a list of compiler option candidates to adopt, use that as the initial list.</li>
688
+
<li>There's already a <ahref="https://best.openssf.org/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++">list of compiler option candidates to adopt</a>, use that as the initial list.</li>
689
689
<li>Do some performance evaluation for how each compiler option affects performance (using CPython's existing performance suite). Report back on the performance impact of enabling each option.</li>
690
-
<li>Implement a small custom tool (proposed in the existing issue) that allows ignoring existing violations of compiler options while preventing future violations. At this point we've achieved a lot of value, all future CPython contributions will have these compiler options applied.</li>
690
+
<li>Implement a small custom tool (proposed in the <ahref="https://github.com/python/cpython/issues/112301">existing issue</a>) that allows ignoring existing violations of compiler options while preventing future violations. At this point we've achieved a lot of value, all future CPython contributions will have these compiler options applied.</li>
691
691
<li>After the tooling is integrated, fill the rest of the project time by remediating known issues.</li>
0 commit comments