| /openbsd-src/gnu/llvm/llvm/docs/ |
| H A D | SecurityTransparencyReports.rst | 5 This page lists the yearly LLVM Security group transparency reports. 28 In 2021, the security group received 13 issue reports that were made publicly 30 reports to be security issues: 57 * https://bugs.chromium.org/p/llvm/issues/detail?id=17 reports a miscompile in 61 * https://bugs.chromium.org/p/llvm/issues/detail?id=19 reports a vulnerability 64 * https://bugs.chromium.org/p/llvm/issues/detail?id=23 reports a new Spectre 68 * https://bugs.chromium.org/p/llvm/issues/detail?id=30 reports missing memory 72 * https://bugs.chromium.org/p/llvm/issues/detail?id=33 reports the RETBLEED
|
| H A D | ReportingGuide.rst | 6 incidents. We consider reports an opportunity for us to act: by knowing about 13 would much rather have reports where we decide to take no action, rather than 23 irc/discord/slack, etc) we ask that you make any reports by emailing 75 All reports will be kept confidential with details shared only with the Code of 78 conversations, and they will not have access to any reports at any time. 87 cases, we can compile several anonymized reports into a pattern of behavior, 90 Transparency reports will be published but will retain confidentiality. See the
|
| H A D | ResponseGuide.rst | 11 All responses to Code of Conduct reports will be managed by a Code of Conduct 24 reports. 97 7. All reports, data, notes, and resolutions are logged in a private location 101 only publish :ref:`transparency reports<Transparency Reports>`. If a public 117 All incident reports should be assessed if they require immediate response and 242 to act on reports involving well-known people in the community. However, if a 259 All reports will be kept confidential with details shared only with the Code of 263 from ongoing conversations, and they will not have access to reports after the 281 reports, if reports are received, after major events (such as the LLVM 287 * An overview of the reports received, and resolutions. [all …]
|
| /openbsd-src/gnu/llvm/llvm/utils/lit/lit/ |
| H A D | cl_arguments.py | 7 import lit.reports 71 type=lit.reports.JsonReport, 119 type=lit.reports.XunitReport, 122 type=lit.reports.ResultDBReport, 125 type=lit.reports.TimeTraceReport, 239 …opts.reports = filter(None, [opts.output, opts.xunit_xml_output, opts.resultdb_output, opts.time_t…
|
| H A D | main.py | 17 import lit.reports 120 for report in opts.reports: 148 tests.sort(key=lit.reports.by_suite_and_test_path)
|
| /openbsd-src/gnu/llvm/clang/docs/analyzer/user-docs/ |
| H A D | CrossTranslationUnit.rst | 135 $ CodeChecker analyze --ctu compile_commands.json -o reports 137 compile_commands.json foo.cpp foo.cpp.ast main.cpp reports/ 138 $ tree reports 139 reports 155 $ CodeChecker parse reports 175 Total number of reports: 1 182 $ CodeChecker parse -e html -o html_out reports 195 …ze-build: Run 'scan-view /tmp/scan-build-2019-07-17-17-53-33-810365-7fqgWk' to examine bug reports. 321 $ CodeChecker analyze --ctu --ctu-ast-loading-mode on-demand compile_commands.json -o reports 323 compile_commands.json foo.cpp main.cpp reports/ [all …]
|
| /openbsd-src/usr.bin/usbhidctl/ |
| H A D | usbhid.c | 646 struct Sreport reports[REPORT_MAXVAL + 1]; in devshow() local 649 for (repind = 0; repind < (sizeof(reports) / sizeof(*reports)); in devshow() 651 reports[repind].status = srs_uninit; in devshow() 652 reports[repind].buffer = NULL; in devshow() 702 repptr = &reports[repindex]; in devshow() 720 for (repind = 0; repind < (sizeof(reports) / sizeof(*reports)); in devshow() 722 setreport(&reports[repind], hidfd, repind); in devshow() 723 freereport(&reports[repind]); in devshow()
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/testsuite/g++.old-deja/g++.robertl/ |
| H A D | README | 1 This directory contains a hodgepodge of problem reports that appeared on 2 the egcs-bugs or egcs mailing lists. Just like the reports themselves,
|
| /openbsd-src/gnu/llvm/clang/docs/ |
| H A D | SourceBasedCodeCoverage.rst | 34 * Creating coverage reports. 65 supported. Uninstrumented code simply won't be accounted for in reports. 134 Creating coverage reports 138 coverage reports. This is done using the "merge" tool in ``llvm-profdata`` 146 There are multiple different ways to render coverage reports. The simplest 221 reports in a directory structure, and generating html reports. For the full 251 Interpreting reports 263 instantiations. This statistic is hidden by default in reports, but can be 309 Impact of llvm optimizations on coverage reports 377 Collecting coverage reports for the llvm project [all …]
|
| H A D | AddressSanitizer.rst | 74 subsequent reports. 125 file\:line info in the AddressSanitizer reports. 243 :doc:`SanitizerSpecialCaseList`, that can be used to suppress error reports 246 suppress error reports for out-of-bound access to globals with certain 249 You may use an ``init`` category to suppress reports about initialization-order 254 # Suppress error reports for code in a file or in a function: 272 Memory leak reports produced by :doc:`LeakSanitizer` (if it is run as a part
|
| H A D | MemorySanitizer.rst | 110 reports. Make sure that ``llvm-symbolizer`` binary is in ``PATH``, 155 reports. It slows down program execution by a factor of 1.5x-2x on top 167 underlying memory will lead to error reports in runtime. Refer to the standard 182 Failing to achieve this may result in false reports.
|
| /openbsd-src/gnu/usr.bin/perl/lib/unicore/ |
| H A D | NamedSqProv.txt | 7 # For documentation, see https://www.unicode.org/reports/tr44/ 32 # Sequences, at https://www.unicode.org/reports/tr34/
|
| /openbsd-src/gnu/gcc/gcc/doc/ |
| H A D | bugreport.texi | 11 Your bug reports play an essential role in making GCC reliable. 42 compiler reports errors (not just warnings) which would ordinarily 93 submit bug reports. Copies of this file in HTML (@file{bugs.html}) and
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/doc/ |
| H A D | bugreport.texi | 11 Your bug reports play an essential role in making GCC reliable. 42 compiler reports errors (not just warnings) which would ordinarily 93 submit bug reports. Copies of this file in HTML (@file{bugs.html}) and
|
| H A D | contrib.texi | 35 Giovanni Bajo for analyzing lots of complicated C++ problem reports. 47 Wolfgang Bangerth for processing tons of bug reports. 117 issues, and keeping up with the problem reports. 229 Christian Ehrhardt for dealing with bug reports. 303 Dara Hazeghi for wading through myriads of target-specific bug reports. 336 Falk Hueffner for working on C and optimization bug reports. 451 Oskar Liljeblad for hacking on AWT and his many Java bug reports and 471 bug reports, prototype patches, and keeping the GNU/Linux ports working. 632 Andrew Pinski for processing bug reports by the dozen. 650 Volker Reichelt for keeping up with the problem reports. [all …]
|
| /openbsd-src/gnu/llvm/llvm/cmake/modules/ |
| H A D | CoverageReport.cmake | 1 # if coverage reports are not enabled, skip all of this 41 set(LLVM_COVERAGE_SOURCE_DIRS "" CACHE STRING "Source directories to restrict coverage reports to.")
|
| /openbsd-src/gnu/usr.bin/perl/dist/Dumpvalue/t/ |
| H A D | extend-coverage.t | 215 is( $x[0], length($five), 'scalarUsage reports length correctly' ); 220 is( $y[0], length($five), 'scalarUsage reports length correctly' ); 225 is ($x[1], length($six), 'scalarUsage reports length of first element correctly' ); 230 is ($y[1], length($six), 'scalarUsage reports length of first element correctly' ); 236 'scalarUsage reports sum of length of array elements correctly' ); 242 'scalarUsage reports length of first element correctly' ); 248 'scalarUsage reports sum of length of hash keys and values correctly' ); 254 'scalarUsage reports sum of length of hash keys and values correctly' );
|
| /openbsd-src/gnu/usr.bin/perl/dist/Thread-Queue/t/ |
| H A D | 11_limit.t | 44 # (6) Get reports from main 46 is_deeply(\@items, [4, 3, 4, 3, 'go'], 'Queue reports');
|
| /openbsd-src/etc/ |
| H A D | motd | 7 version of the code. With bug reports, please try to ensure that
|
| /openbsd-src/regress/usr.bin/diff/ |
| H A D | t5.2 | 7 version of the code. With bug reports, please try to ensure that
|
| H A D | t6.2 | 7 version of the code. With bug reports, please try to ensure that
|
| H A D | t7.2 | 7 version of the code. With bug reports, please try to ensure that
|
| H A D | t7.1 | 7 version of the code. With bug reports, please try to ensure that
|
| H A D | t6.1 | 7 version of the code. With bug reports, please try to ensure that
|
| H A D | t5.1 | 7 version of the code. With bug reports, please try to ensure that
|