| /openbsd-src/gnu/llvm/llvm/docs/ |
| H A D | SecurityTransparencyReports.rst | 2 LLVM Security Group Transparency Reports
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 | ResponseGuide.rst | 11 All responses to Code of Conduct reports will be managed by a Code of Conduct
24 reports.
35 Reports are typically received by email (conduct@llvm.org) or in person from
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
273 .. _Transparency Reports:
[all …]
|
| 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
|
| /openbsd-src/sys/netinet/ |
| H A D | igmp_var.h | 59 u_long igps_rcv_reports; /* received membership reports */
60 u_long igps_rcv_badreports; /* received invalid reports */
61 u_long igps_rcv_ourreports; /* received reports for our groups */
62 u_long igps_snd_reports; /* sent membership reports */
86 igps_rcv_reports, /* received membership reports */
87 igps_rcv_badreports, /* received invalid reports */
88 igps_rcv_ourreports, /* received reports for our groups */
89 igps_snd_reports, /* sent membership reports */
|
| /openbsd-src/gnu/llvm/clang/include/clang/StaticAnalyzer/Core/BugReporter/ |
| H A D | BugReporter.h | 65 // Interface for individual bug reports.
118 /// individual bug reports.
193 /// identical reports that have different uniqueing decls will be considered
246 /// Reports are uniqued to ensure that we do not emit multiple diagnostics
304 /// Profile to identify equivalent bug reports for error report coalescing.
333 /// path. This is useful for some reports that want maximum fidelty
353 /// Reports with different uniqueing locations are considered to be different
381 /// The reports that have the same report location, description, bug type, and
382 /// ranges are uniqued - only one of the equivalent reports will be presented
384 /// for uniquing reports. For example, memory leaks checker, could set this to
[all …]
|
| /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/gnu/llvm/clang/www/analyzer/ |
| H A D | codechecker.html | 36 CodeChecker analyze compile_commands.json -o ./reports
44 CodeChecker parse --print-steps ./reports
48 CodeChecker parse ./reports -e html -o ./reports_html
58 CodeChecker store ./reports --name my-project --url http://localhost:8555/Default
|
| H A D | filing_bugs.html | 18 <p>We encourage users to file bug reports for any problems that they encounter.
48 reports to Apple's <a href="https://feedbackassistant.apple.com/welcome">Feedback Assistant</a> web
52 attractive than filing bug reports through Bugzilla as not everyone who works on
|
| /openbsd-src/gnu/llvm/llvm/tools/llvm-cov/ |
| H A D | CoverageReport.h | 39 /// Prepare file reports for the files specified in \p Files.
54 /// Render file reports for every unique file in the coverage mapping.
58 /// Render file reports for the files specified in \p Files.
61 /// Render file reports for the files specified in \p Files and the functions
|
| /openbsd-src/gnu/llvm/clang/utils/analyzer/ |
| H A D | CmpRuns.py | 5 which reports have been added, removed, or changed.
9 1. To monitor changes in the static analyzer's reports on real code bases,
212 self.reports: List[AnalysisReport] = []
213 # Cumulative list of all diagnostics from all the reports.
230 # reports. Assume that all reports were created using the same
238 # Ignore/delete empty reports.
244 # Extract the HTML reports, if they exists.
265 self.reports.append(report)
474 for report in results.reports:
610 out.write(f"TOTAL REPORTS: {total_reports}\n")
[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,
120 help="Write XUnit-compatible XML test reports to the specified file")
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…
|
| /openbsd-src/gnu/llvm/clang/docs/ |
| H A D | AddressSanitizer.rst | 74 subsequent reports.
84 Symbolizing the Reports
125 file\:line info in the AddressSanitizer reports.
175 Suppressing Reports in External Libraries
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 | 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 …]
|
| /openbsd-src/usr.bin/sendbug/ |
| H A D | sendbug.1 | 17 is used to submit problem reports (PRs) to the
53 The status of bug reports can be followed by checking the
68 This information is very helpful in reports,
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/doc/ |
| 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 …]
|
| 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/sys/dev/pci/drm/i915/ |
| H A D | i915_perf.c | 75 * the constraints on HW configuration require reports to be filtered before it
114 * The OA unit writes reports of counters into a circular buffer, without
134 * feature and forwarded OA reports to userspace via perf's 'raw' sample
138 * them. For Mesa it's also convenient to be forwarded raw, periodic reports
139 * for combining with the side-band raw reports it captures using
169 * attach GPU timestamps to our OA samples. We were shoehorning OA reports
238 * Although this can be observed explicitly while copying reports to userspace
239 * by checking for a zeroed report-id field in tail reports, we want to account
243 * We workaround this issue in oa_buffer_check_unlocked() by reading the reports
259 * non-periodic reports (suc
[all...] |
| /openbsd-src/gnu/llvm/clang/tools/scan-build/man/ |
| H A D | scan-build.1 | 29 .Op Fl no-failure-reports
82 created in /tmp (TMPDIR on Mac OS X) to store the reports.
123 .It Fl no-failure-reports
126 subdirectory that includes analyzer crash reports and preprocessed
333 The above example causes analysis reports to be deposited into
|
| /openbsd-src/gnu/usr.bin/cvs/man/ |
| H A D | cvsbug.8 | 54 .I problem reports
116 Change mail address at the support site for problem reports. The
155 to submit problem reports rather than mailing them directly. Using
175 Problem reports have to be in a particular form so that a program can
|
| /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/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 | 39 Giovanni Bajo for analyzing lots of complicated C++ problem reports.
55 Wolfgang Bangerth for processing tons of bug reports.
139 the frustrating localization issues, and keeping up with the problem reports.
265 Christian Ehrhardt for dealing with bug reports.
345 Dara Hazeghi for wading through myriads of target-specific bug reports.
381 Falk Hueffner for working on C and optimization bug reports.
510 Oskar Liljeblad for hacking on AWT and his many Java bug reports and
530 bug reports, prototype patches, and keeping the GNU/Linux ports working.
699 Andrew Pinski for processing bug reports by the dozen.
720 Volker Reichelt for keeping up with the problem reports.
[all …]
|
| /openbsd-src/usr.sbin/lpr/lpq/ |
| H A D | lpq.1 | 49 for printing files on the line printer, and reports the status of the
53 without any arguments reports on any jobs currently in the queue.
77 reports the user's name, current rank in the queue, the
|
| /openbsd-src/gnu/usr.bin/perl/cpan/PerlIO-via-QuotedPrint/lib/PerlIO/via/ |
| H A D | QuotedPrint.pm | 97 Patches, bug reports, suggestions or any other feedback is welcome.
102 Bug reports and suggestions can be made on the CPAN Request Tracker at
108 Please test this distribution. See CPAN Testers Reports at
111 Previous test results on CPAN Testers Reports can be viewed at
|
| /openbsd-src/etc/examples/ |
| H A D | sensorsd.conf | 31 # By default, sensorsd(8) reports status changes of all sensors that
33 # suppress reports about status changes of specific sensor types.
|