Home
last modified time | relevance | path

Searched refs:wording (Results 1 – 25 of 73) sorted by relevance

123

/openbsd/src/gnu/gcc/gcc/
Dtree-ssa-loop-niter.c1142 const char *wording; in number_of_iterations_exit() local
1152 wording = in number_of_iterations_exit()
1157 wording = in number_of_iterations_exit()
1163 warning (OPT_Wunsafe_loop_optimizations, "%H%s", &loc, gettext (wording)); in number_of_iterations_exit()
1165 warning (OPT_Wunsafe_loop_optimizations, "%s", gettext (wording)); in number_of_iterations_exit()
Dloop-iv.c2690 const char *wording; in get_simple_loop_desc() local
2698 wording = in get_simple_loop_desc()
2703 gettext (wording)); in get_simple_loop_desc()
2707 wording = in get_simple_loop_desc()
2712 gettext (wording)); in get_simple_loop_desc()
/openbsd/src/share/zoneinfo/datfiles/
Dzonenow.tab19 # 4. Every timezone has a nonempty comments column, with wording
/openbsd/src/gnu/lib/libstdc++/libstdc++/docs/html/17_intro/
Dlibstdc++-assign.txt14 license software produced there will do. Here is a sample wording:
/openbsd/src/gnu/llvm/llvm/docs/
DCodeOfConduct.rst171 based on wording from the `Speak Up! project`_.)
DMyFirstTypoFix.rst43 This is clear enough, but not exactly catchy. Let's improve the wording
/openbsd/src/gnu/llvm/clang/docs/
DBlock-ABI-Apple.rst21 * 2010/4/6 - improved wording.
22 * 2013/1/6 - improved wording and converted to rst.
/openbsd/src/gnu/usr.bin/perl/pod/
Dperl5300delta.pod823 digits". This means the same wording is used for this kind of error as
831 digits". This means the same wording is used for this kind of error as
1232 A few error messages have minor wording changes. This is essentially
Dperl5380delta.pod965 Some wording improvements have been made for the C<ucfirst>, C<push>,
1005 Added a section on "Scoping Rules of Regex Variables", and other wording
1479 wording changes between the C<@INC> and C<:>, for instance use
Dperlpod.pod771 Older translators might add wording around an LE<lt>E<gt> link, so that
Dperlsec.pod474 blah." You should see a lawyer to be sure your license's wording will
/openbsd/src/gnu/usr.bin/binutils/gdb/doc/
DChangeLog111 * gdb.texinfo (Edit): Fix markup of EDITOR and improve wording.
1556 * gdb.texinfo (Memory Region Attributes): Fix the wording.
1712 * gdb.texinfo (Free Software): Fix wording.
2345 * agentexpr.texi: Fix wording regarding Intel's IA-64
2387 * gdb.texinfo: Various minor wording and formatting improvements,
2700 * remote.texi: Changed wording that implied that the GDB remote
3953 * stabs.texinfo: Minor wording changes.
/openbsd/src/gnu/usr.bin/cvs/doc/
DChangeLog699 * cvs.texinfo (tag): Remove confusing wording about supplying
961 more advanced topic and the "but see" wording didn't tell us what
1395 * cvs.texinfo (Error messages): Add comment about wording of error
2040 * cvs.texinfo (Error messages): Give exact wording of broken pipe
2146 vs. remsh. Also wording fix ("incorrect" -> "inapplicable").
2459 number" section to tighten up the wording, better motivate the
2950 Add comment about that infernal "short as possible" wording.
/openbsd/src/gnu/usr.bin/gcc/contrib/
DChangeLog125 Simplify and reformat introductory wording.
/openbsd/src/gnu/usr.bin/cvs/
DChangeLog787 * NEWS: Add item about PreservePermissions. Fix unclear wording
959 * FAQ: Re-import from FAQ-O-Matic. Features a wording fix to
1541 the ability to send to the list (the new wording was approved by
1994 mention portable once, and other wording cleanups.
2326 longer different for VMS). Various wording fixes to reflect the
/openbsd/src/gnu/gcc/gcc/cp/
DChangeLog-1993524 * cp-typeck.c (build_indirect_ref): Improve wording on error
DChangeLog-199557 * method.c (report_type_mismatch): Improve wording for volatile
491 * init.c (resolve_offset_ref): Fix wording of non-static member
2953 exception_specification_opt to match draft wording. Use maybe_init
DChangeLog-1996331 * error.c (dump_expr): Improve the wording on error messages that
444 * typeck.c (get_delta_difference): Fix wording, as we can be used
2475 * call.c (build_method_call): Fix wording of error messages so
/openbsd/src/gnu/usr.bin/perl/dist/Devel-PPPort/
DChanges853 * improve wording baseline information
/openbsd/src/gnu/usr.bin/perl/cpan/Pod-Simple/t/
Dperlfaq.pod575 you want to be sure your license's wording will stand up in court.
Dperlfaqo.txt180 …course, so you should see a lawyer if you want to be sure your license's wording will stand up in …
/openbsd/src/gnu/usr.bin/cvs/src/
DChangeLog-971486 (binfiles, binfiles2): Adjust to reflect wording change from
2192 * history.c (history_usg): Add comment about message wording.
2341 * root.c (check_root_consistent): Add comment about wording of
/openbsd/src/gnu/usr.bin/binutils/etc/
Dstandards.texi116 suggested new wording for it; our time is limited. We prefer a context
899 distribution terms, and changing the rest of the wording as necessary.
3401 outline structure, wording, tables or examples from preexisting non-free
/openbsd/src/gnu/usr.bin/binutils-2.17/etc/
Dstandards.texi116 suggested new wording for it; our time is limited. We prefer a context
899 distribution terms, and changing the rest of the wording as necessary.
3401 outline structure, wording, tables or examples from preexisting non-free
/openbsd/src/games/fortune/datfiles/
Dfortunes-o378 "Dear Mr. Seldes: I cannot remember the exact wording of the statement
1935 wording: "Miss Brown, I'd like to introduce you to an older person"

123