Home
last modified time | relevance | path

Searched refs:issue (Results 1 – 25 of 681) sorted by relevance

12345678910>>...28

/openbsd-src/gnu/llvm/clang/www/
H A Dmake_cxx_dr_status11 def __init__(self, section, issue, url, status, title): argument
12 self.section, self.issue, self.url, self.status, self.title = \
13 section, issue, url, status, title
15 return '%s (%s): %s' % (self.issue, self.status, self.title)
26 _, url, issue = issue_link.split('"', 2)
28 issue = int(issue.split('>', 1)[1].split('<', 1)[0])
30 return DR(section, issue, url, status, title)
66 key = lambda dr: dr.issue)
126 def availability(issue): argument
127 status = status_map.get(issue, 'unknown')
[all …]
/openbsd-src/gnu/gcc/gcc/config/sh/
H A Dsh4.md49 ;; Since SH4 is a dual issue machine,it is as if there are two
77 ;; complete in 0 cycles. So we use an extra unit for the issue of LS insns.
81 ;; This will be reserved after "issue" of branch instructions
88 ;; This reservation is to simplify the dual issue description.
90 (define_reservation "issue" "pipe_01|pipe_02")
93 ;; Note that the issue of a CO group insn also effectively locks the D stage.
97 ;; Every FE instruction but fipr / ftrv starts with issue and this.
121 "issue")
128 "issue+load_store")
130 ;; We don't model all pipeline stages; we model the issue ('D') stage
[all …]
H A Dshmedia.md24 ;; single-issue machine. It has four pipelines, the branch unit (br),
34 ;; Every instruction on SH-5 occupies the issue resource for at least one
88 ;; can continue to issue.
/openbsd-src/gnu/llvm/llvm/utils/git/
H A Dgithub-automation.py30 self.issue = self.repo.get_issue(issue_number)
38 self.issue.create_comment(comment)
185 def issue(self) -> github.Issue.Issue: member in ReleaseWorkflow
198 issue = self.issue
199 milestone = issue.milestone
211 self.issue.create_comment('/branch {}/{}'.format(self.branch_repo_name, self.branch_name))
214 self.issue.create_comment('/pull-request {}#{}'.format(self.branch_repo_name, pull.number))
227 self.issue.create_comment(self.make_ignore_comment(message))
241 issue = self.issue
242 comment = issue.create_comment(message)
[all …]
/openbsd-src/gnu/llvm/llvm/docs/
H A DSecurity.rst16 …issue reporter and key experts) while an issue is being investigated. After an issue becomes publi…
18 .. _report-security-issue:
20 How to report a security issue?
23 To report a security issue in the LLVM Project, please `open a new issue`_ in the LLVM project page…
25 …ion mailing list is public**: avoid discussing or mentioning the specific issue when posting on it.
79 …- If already in the LLVM Security Group, has actively participated in one (if any) security issue …
91 … fully-world-readable nomination seems inappropriate, you may `open a new issue`_, and a discussio…
133 Members of the LLVM Security Group will be expected to treat LLVM security issue information shared…
135 * Members should not disclose security issue information to non-members unless both members are emp…
136 …ducts if their product suffers from the same issue. The non-LLVM vendor should be asked to respect…
[all …]
H A DBugLifeCycle.rst56 unless the issue is being :ref:`closed<Closing>`.
81 * If the issue is with a particular revision of the C or C++ standard, please
88 * Add the ``good first issue`` label if you think this would be a good bug to
112 * If the issue has been resolved by a particular commit, close the issue with
115 ``Fixes #<issue number>`` on a line by itself. GitHub recognizes such commit
116 messages and will automatically close the specified issue with a reference
119 * If the reported behavior is not a bug, it is appropriate to close the issue
123 * If the bug duplicates another issue, close it as a duplicate by adding the
124 ``duplicate`` label with a comment pointing to the issue it duplicates.
126 * If there is a sound reason for not fixing the issue (difficulty, ABI, open
[all …]
H A DGitHub.rst22 following commands on any issue that has been added to one of the "X.Y.Z Release"
32 the issue. If the commit(s) do apply cleanly, then a pull request will
H A DGitRepositoryPolicy.md5 cases please create an issue with the
25 To request a new repository, please create an issue with the
H A Dindex.rst90 Reporting a security issue
92 * :ref:`report-security-issue`
/openbsd-src/gnu/usr.bin/perl/pod/
H A Dperlsecpolicy.pod46 If your report meets the team's criteria, an issue will be opened in the
47 team's private issue tracker and you will be provided the issue's ID number.
52 issue and guide you through any further action that is required to complete
62 A security issue is a bug in one or more specific components of a software
96 bundled with Perl, we will assist in forwarding the issue to the relevant
106 criteria to be considered a security issue:
113 or public issue tracker.
181 This type of bug is a long standing issue with the Perl interpreter
223 quirks that are extensively documented in Perl's public issue tracker.
284 When you report a security issue privately to the
[all …]
H A Dperldelta.pod46 this document. If you find any we have missed, open an issue at
101 Fixed an issue where C<utf8n_to_uvchr()> failed to correctly identify certain
151 If you believe you have an unreported bug, please open an issue at
156 inappropriate to send to a public issue tracker, then see
158 report the issue.
/openbsd-src/gnu/gcc/gcc/config/mips/
H A D5k.md9 ;; 5Kc - Single issue with no floating point unit.
10 ;; 5kf - Separate floating point pipe which can dual-issue with the
118 ;; Any -> JR/JALR (without dependency) : 1 clock issue delay
119 ;; Any -> JR/JALR (with dependency) : 2 clock issue delay
120 ;; load -> JR/JALR (with dependency) : 3 clock issue delay
121 ;; mfhilo -> JR/JALR (with dependency) : 3 clock issue delay
122 ;; mul -> JR/JALR (with dependency) : 3 clock issue delay
128 ;; Unknown or multi - single issue
136 ;; The 5Kf is a partial dual-issue cpu which can dual issue an integer
226 ;; fxfer (mfc1, mfhc1, mtc1, mthc1) - single issue
H A Dsb1.md7 ;; pipes, and 1 MDMX pipes. It can issue 2 ls insns and 2 exe/fpu/mdmx insns
10 ;; We model the 4-way issue by ordering unit choices. The possible choices are
11 ;; {ex1,fp1}|{ex0,fp0}|ls1|ls0. Instructions issue to the first eligible unit
12 ;; in the list in most cases. Non-indexed load/stores issue to ls0 first.
13 ;; simple alu operations issue to ls1 if it is still available, and their
14 ;; operands are ready (no co-issue with loads), otherwise to the first
17 ;; When exceptions are enabled, can only issue FP insns to fp1. This is
21 ;; In 32-bit mode, dependent FP can't co-issue with load, and only one FP exe
22 ;; insn can issue per cycle (fp1).
53 ;; Can only issue to one of the ex and fp pipes at a time.
[all …]
/openbsd-src/gnu/usr.bin/gcc/gcc/config/alpha/
H A Dev6.md21 ; EV6 can issue 4 insns per clock. It's out-of-order, so this isn't
31 ; all EBOX insn_reservations that can issue to either cluster, increasing
34 ; ??? In addition, instruction order affects cluster issue.
52 ; Integer loads take at least 3 clocks, and only issue to lower units.
88 ; Motion video insns also issue only to U0, and take three ticks.
94 ; Shifts issue to upper units.
100 ; Multiplies issue only to U1, and all take 7 ticks.
113 ; Integer branches issue to upper units
119 ; Calls only issue to L0.
125 ; Ftoi/itof only issue to lower pipes.
/openbsd-src/gnu/gcc/gcc/config/alpha/
H A Dev6.md21 ; EV6 can issue 4 insns per clock. It's out-of-order, so this isn't
31 ; all EBOX insn_reservations that can issue to either cluster, increasing
34 ; ??? In addition, instruction order affects cluster issue.
52 ; Integer loads take at least 3 clocks, and only issue to lower units.
93 ; Motion video insns also issue only to U0, and take three ticks.
99 ; Shifts issue to upper units.
105 ; Multiplies issue only to U1, and all take 7 ticks.
118 ; Integer branches issue to upper units
124 ; Calls only issue to L0.
130 ; Ftoi/itof only issue to lower pipes.
/openbsd-src/gnu/usr.bin/perl/
H A DSECURITY.md29 If your report meets the team's criteria, an issue will be opened in the
30 team's private issue tracker and you will be provided the issue's ID number.
35 issue and guide you through any further action that is required to complete
/openbsd-src/gnu/usr.bin/perl/Porting/
H A Dsecurity_template.pod5 Not every heading below is appropriate for every security issue, so
16 FIXME - short description of the security issue, with an identifier of the issue as the manpage name
31 =head2 Who is particularly vulnerable because of this issue?
/openbsd-src/gnu/llvm/llvm/lib/Target/AArch64/
H A DAArch64SchedKryo.td15 // The issue width is set to five, matching the five issue queues for expanded
17 // but these do not actually take up an issue queue.
20 let IssueWidth = 5; // 5-wide issue for expanded uops
21 let MicroOpBufferSize = 128; // Out-of-order with temporary unified issue buffer
/openbsd-src/usr.bin/awk/
H A DFIXES44 for spotting the ARGV issue and Todd Miller for the fix.
50 Fixed regex engine gototab reallocation issue that was
53 character. Thanks to Oguz Ismail for spotting the issue.
58 the issue and providing a fix, and to Miguel Pineiro Jr.
81 Fix issue #199: gototab improvements to dynamically resize the
113 unicode FS and RS. Also fixed gsub null match issue with unicode.
/openbsd-src/gnu/llvm/clang/utils/analyzer/
H A DCmpRuns.py325 def add_common(self, issue: AnalysisDiagnostic):
326 self.present_in_both.append(issue)
328 def add_removed(self, issue: AnalysisDiagnostic):
329 self.present_only_in_old.append(issue)
331 def add_added(self, issue: AnalysisDiagnostic):
332 self.present_only_in_new.append(issue)
/openbsd-src/gnu/usr.bin/gcc/gcc/config/sparc/
H A Dultra1_2.md21 ;; UltraSPARC-I and II are quad-issue processors. Interesting features
32 ;; former must be issued first in order for both of them to issue.
33 ;; - Stores can issue before the value being stored is available. As long
36 ;; - Branches may issue in the same cycle as an instruction setting the
55 ;; This is a simplified representation of the issue at hand.
243 ;; Any store may multi issue with the insn creating the source
/openbsd-src/gnu/gcc/gcc/config/sparc/
H A Dultra1_2.md21 ;; UltraSPARC-I and II are quad-issue processors. Interesting features
32 ;; former must be issued first in order for both of them to issue.
33 ;; - Stores can issue before the value being stored is available. As long
36 ;; - Branches may issue in the same cycle as an instruction setting the
55 ;; This is a simplified representation of the issue at hand.
243 ;; Any store may multi issue with the insn creating the source
/openbsd-src/gnu/usr.bin/binutils-2.17/cpu/
H A Dfrv.cpu72 1 1 ; issue done
109 1 1 ; issue done
117 1 1 ; issue done
125 1 1 ; issue done
133 1 1 ; issue done
141 1 1 ; issue done
150 1 1 ; issue done
159 1 1 ; issue done
167 1 1 ; issue done
177 1 3 ; issue done
[all …]
/openbsd-src/gnu/llvm/libcxx/cmake/caches/
H A DGeneric-asan.cmake2 # This is a temporary (hopefully) workaround for an ASan issue (see https://llvm.org/D119410).
/openbsd-src/gnu/usr.bin/binutils/cpu/
H A Dfrv.cpu72 1 1 ; issue done
109 1 1 ; issue done
117 1 1 ; issue done
125 1 1 ; issue done
133 1 1 ; issue done
141 1 1 ; issue done
150 1 1 ; issue done
159 1 1 ; issue done
167 1 1 ; issue done
177 1 3 ; issue done
[all …]

12345678910>>...28