| /netbsd-src/sys/dev/microcode/aic7xxx/ |
| H A D | aic79xx_seq.h | 802 return ((ahd->bugs & AHD_PKT_BITBUCKET_BUG) != 0); in ahd_patch22_func() 810 return ((ahd->bugs & AHD_PKT_BITBUCKET_BUG) == 0); in ahd_patch21_func() 842 return ((ahd->bugs & AHD_AUTOFLUSH_BUG) != 0); in ahd_patch17_func() 882 return ((ahd->bugs & AHD_REG_SLOW_SETTLE_BUG) != 0); in ahd_patch12_func() 890 return ((ahd->bugs & AHD_EARLY_REQ_BUG) != 0); in ahd_patch11_func() 898 return ((ahd->bugs & AHD_BUSFREEREV_BUG) == 0); in ahd_patch10_func() 914 return ((ahd->bugs & AHD_LQO_ATNO_BUG) != 0); in ahd_patch8_func() 922 return ((ahd->bugs & AHD_BUSFREEREV_BUG) != 0); in ahd_patch7_func() 930 return ((ahd->bugs & AHD_NONPACKFIFO_BUG) != 0); in ahd_patch6_func() 938 return ((ahd->bugs & AHD_SENT_SCB_UPDATE_BUG) != 0); in ahd_patch5_func() [all …]
|
| H A D | aic7xxx_seq.h | 906 return ((ahc->bugs & AHC_SCBCHAN_UPLOAD_BUG) != 0); in ahc_patch23_func() 946 return ((ahc->bugs & AHC_PCI_2_1_RETRY_BUG) != 0); in ahc_patch18_func() 962 return ((ahc->bugs & AHC_AUTOFLUSH_BUG) != 0); in ahc_patch16_func() 978 return ((ahc->bugs & AHC_PCI_MWI_BUG) != 0 && ahc->pci_cachesize != 0); in ahc_patch14_func()
|
| /netbsd-src/external/gpl3/binutils/dist/binutils/ |
| H A D | SECURITY.txt | 10 bugs might occur. In the first, the programs themselves might be 15 Other than that, all other bugs will be treated as non-security 17 they will not be given the priority that is given to security bugs. 22 to be security bugs, since they do not create executable output 37 Reporting private security bugs 40 *All bugs reported in the Binutils Bugzilla are public.* 45 such bugs: 61 Reporting public security bugs 64 It is expected that critical security bugs will be rare, and that most 65 security bugs can be reported in Binutils Bugzilla system, thus making
|
| /netbsd-src/external/apache2/llvm/dist/llvm/docs/ |
| H A D | BugLifeCycle.rst | 13 We aim to achieve a basic level of consistency in how reported bugs evolve from 19 At the same time, we aim to not over-specify the life cycle of bugs in the 20 `the LLVM Bug Tracking System <https://bugs.llvm.org/enter_bug.cgi>`_, as the 31 newly reported bugs or what the breakdown into products & components is we use, 40 Reporting bugs 56 Triaging bugs 90 Actively working on fixing bugs 99 Resolving/Closing bugs 102 For simplicity, we only have 1 status for all resolved or closed bugs: 105 Resolving bugs is good! Make sure to properly record the reason for resolving.
|
| H A D | FuzzingLLVM.rst | 24 bugs this fuzzer has reported are `on bugzilla`__ and `on OSS Fuzz's 28 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+clang-fuzzer 48 bugs this fuzzer has reported are `on bugzilla`__ 53 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+clang-format-fuzzer 59 Some of the bugs this fuzzer has reported are `on bugzilla`__. 67 :doc:`llvm-dwarfdump <CommandGuide/llvm-dwarfdump>` on them. Some of the bugs 70 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+llvm-dwarfdump-fuzzer 82 A |LLVM IR fuzzer| aimed at finding bugs in instruction selection. 107 A |LLVM IR fuzzer| aimed at finding bugs in optimization passes. 233 one sanitizer to find bugs faster. The most common way to build the fuzzers is [all …]
|
| H A D | HowToSubmitABug.rst | 5 Introduction - Got bugs? 23 <https://bugs.llvm.org/enter_bug.cgi>`_ and fill out the form with the 25 the "new-bugs" category if you're not sure). The bug description should 40 More often than not, bugs in the compiler cause it to crash---often due to 53 the crash is in the front-end. Jump ahead to :ref:`front-end bugs 58 :ref:`middle-end bugs <middleend-crash>`. 61 generator bugs <backend-crash>`. 65 Front-end bugs 90 Middle-end optimization bugs 132 Backend code generator bugs [all …]
|
| H A D | ReleaseProcess.rst | 29 * Make sure the critical bugs get fixed and merged to the next release candidate 31 Not all bugs or regressions are show-stoppers and it's a bit of a grey area what 38 or a known bug. Known bugs are "unsupported features" and some bugs can be 41 * The stage in the release. Less critical bugs should be considered to be 137 candidate. You don't need to fix all the bugs in the test-suite, since they're 144 as blocker, and all the other bugs as important, but not necessarily blocking 223 * Critical bugs on compilation should be fixed as soon as possible, possibly
|
| H A D | HowToReleaseLLVM.rst | 46 bugs found during this testing phase will be fixed. Any bugs introduced by 166 bugs, and then number of regressions when determining whether or not to make a 171 kind of bugs that are critical enough to block a release would be a major regression 187 release is out, all bugs reported will have to go on the next stable release. 204 Once all testing has been completed and appropriate bugs filed, the release 241 the time to solve additional and unrelated bugs!* If no patches are merged in, 252 To help manage all the bugs reported and which ones are blockers or not, a new 273 it as a blocker of the current release bug. Release bugs are given aliases 280 .. _bug: https://bugs.llvm.org/ 305 bugs or regressions. [all …]
|
| /netbsd-src/external/gpl3/gcc/dist/maintainer-scripts/ |
| H A D | branch_changer.py | 203 …bugs = Bug.get_bugs(api_key, {'api_key': api_key, 'summary': search_summary, 'bug_status': statuse… 204 bugs = list(filter(lambda x: x.is_regression, bugs)) 207 for bug in bugs: 222 …bugs = Bug.get_bugs(api_key, {'api_key': api_key, 'bug_status': statuses, 'target_milestone': old_… 225 for bug in bugs:
|
| /netbsd-src/external/gpl3/gcc.old/dist/maintainer-scripts/ |
| H A D | branch_changer.py | 177 …bugs = Bug.get_bugs(api_key, {'api_key': api_key, 'summary': search_summary, 'bug_status': statuse… 178 bugs = list(filter(lambda x: x.is_regression, bugs)) 181 for bug in bugs: 195 …bugs = Bug.get_bugs(api_key, {'api_key': api_key, 'bug_status': statuses, 'target_milestone': old_… 198 for bug in bugs:
|
| H A D | bugzilla-close-candidate.py | 61 …bugs = get_bugs(api_key, {'api_key': api_key, 'bug_status': statuses, 'limit': chunk, 'offset': i … 62 for b in sorted(bugs, key = lambda x: x['id'], reverse = True):
|
| /netbsd-src/sys/dev/pci/ |
| H A D | ahc_pci.c | 982 if ((ahc->bugs & AHC_CACHETHEN_DIS_BUG) != 0) in ahc_pci_attach() 985 if ((ahc->bugs & AHC_CACHETHEN_BUG) != 0) in ahc_pci_attach() 994 if ((ahc->bugs & AHC_PCI_2_1_RETRY_BUG) != 0 in ahc_pci_attach() 1469 ahc->bugs |= AHC_TMODE_WIDEODD_BUG|AHC_CACHETHEN_BUG|AHC_PCI_MWI_BUG; in ahc_aic785X_setup() 1472 ahc->bugs |= AHC_PCI_2_1_RETRY_BUG; in ahc_aic785X_setup() 1484 ahc->bugs |= AHC_TMODE_WIDEODD_BUG|AHC_CACHETHEN_BUG|AHC_PCI_MWI_BUG; in ahc_aic7860_setup() 1487 ahc->bugs |= AHC_PCI_2_1_RETRY_BUG; in ahc_aic7860_setup() 1510 ahc->bugs |= AHC_TMODE_WIDEODD_BUG|AHC_CACHETHEN_BUG|AHC_PCI_MWI_BUG; in ahc_aic7870_setup() 1555 ahc->bugs |= AHC_TMODE_WIDEODD_BUG; in ahc_aic7880_setup() 1558 ahc->bugs |= AHC_PCI_2_1_RETRY_BUG; in ahc_aic7880_setup() [all …]
|
| /netbsd-src/crypto/external/bsd/openssh/dist/ |
| H A D | compat.c | 48 int bugs; in compat_banner() member 133 version, check[i].pat, check[i].bugs); in compat_banner() 134 ssh->compat = check[i].bugs; in compat_banner()
|
| /netbsd-src/external/gpl2/xcvs/dist/ |
| H A D | BUGS | 2 report bugs (and what will happen to your bug reports if you do). 4 The following is a list of some of the known bugs. It may or may not 8 manual). There are some other reported bugs in MINOR-BUGS; the 9 difference, at least in theory, is that those bugs are less serious. 13 bugs), see README.VMS, windows-NT/README, or os2/README. There is no 15 This file also might contain some platform-specific bugs. 78 P.S. Is anyone working on fixing these bugs?
|
| /netbsd-src/external/bsd/pdisk/dist/ |
| H A D | HISTORY | 8 documentation, fixing bugs and making it prettier. 10 Fixed a few more bugs. 14 a few more bugs. 28 09/1997 - Fixed bugs in MacOS version of variable block size.
|
| /netbsd-src/external/gpl3/autoconf/dist/ |
| H A D | BUGS | 3 This file lists the bugs you must be aware of. Be sure to check this 14 Autoconf must not be used in production if there are ``Serious'' bugs, 15 and use with caution an Autoconf with ``Important bugs''.
|
| /netbsd-src/external/apache2/llvm/dist/llvm/lib/Target/AVR/ |
| H A D | README.md | 7 * [Unresolved bugs](https://llvm.org/bugs/buglist.cgi?product=libraries&component=Backend%3A%20AVR&…
|
| /netbsd-src/lib/libc/db/ |
| H A D | changelog | 12 btree: Rework cursor deletion code yet again; bugs with 17 btree: Fix bugs introduced by new cursor/deletion code. 21 btree: Fix bugs introduced by new cursor/deletion code. 70 hash: Fixed big key overflow bugs.
|
| /netbsd-src/crypto/external/bsd/heimdal/dist/ |
| H A D | README | 8 Bug reports and bugs are appreciated, see more under Bug reports in 9 the manual on how we prefer them: <heimdal-bugs@h5l.org>.
|
| /netbsd-src/external/gpl3/gdb/dist/gnulib/import/m4/ |
| H A D | memchr.m4 | 17 # Detect platform-specific bugs in some versions of glibc: 21 # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521737 62 /* Test against bugs on glibc systems. */
|
| /netbsd-src/external/lgpl3/mpfr/dist/ |
| H A D | BUGS | 23 Known bugs: 46 Potential bugs: 54 * Possible bugs with huge precisions (> 2^30) and a 32-bit ABI, in particular 57 * Possible bugs if the chosen exponent range does not allow to represent
|
| /netbsd-src/external/bsd/tre/dist/ |
| H A D | NEWS | 86 - Some bugs fixed. 101 - Several bugs and compilation problems fixed. 114 - Fixed bugs: handling null bytes in multibyte mode, exponential 116 a regexp, and bugs in expanding {m,n} repeats (still!). 131 - Fixed bugs which occurred sometimes when "{m,n}" repeats were used 140 - Fixed several bugs related to REG_NOSUB or NULL pmatch[] arrays
|
| /netbsd-src/usr.bin/indent/ |
| H A D | README.md | 15 many inconsistencies and bugs. Several of these bugs had been introduced by
|
| /netbsd-src/external/gpl2/gettext/dist/autoconf-lib-link/tests/ |
| H A D | rpath.README | 35 - bugs in libtool that creates the shared libraries, 36 - bugs in lib-link.m4. 40 - bugs in libtool that creates the shared libraries.
|
| /netbsd-src/external/gpl3/gcc/dist/ |
| H A D | README | 17 See http://gcc.gnu.org/bugs/ for how to report bugs usefully.
|