diff options
| author | Bruno Haible <bruno@clisp.org> | 2019-04-07 13:37:02 +0200 |
|---|---|---|
| committer | Bruno Haible <bruno@clisp.org> | 2019-04-07 16:58:19 +0200 |
| commit | 91584ed612fa26a505c8fc4c7f6fb19f7413795d (patch) | |
| tree | 5111d7866990102e04b97b22dcf3e41f1a8d6eac /lib/memchr2.valgrind | |
| parent | 834bd58e649fc4a271c0c85c40557e04ee161d63 (diff) | |
| download | gnulib-91584ed612fa26a505c8fc4c7f6fb19f7413795d.tar.gz | |
Add copyright notices in several files.
Reported by <ineiev@gnu.org> in <https://savannah.gnu.org/bugs/?54809>.
* lib/_Noreturn.h: Add LGPLv2+ copyright notice.
* lib/libunistring.valgrind: Likewise.
* lib/iconv_open-*.gperf: Add GPLv2+ copyright notice.
* lib/uniname/gen-uninames.lisp: Add GPLv3+ copyright notice.
* lib/memchr.valgrind: Likewise.
* lib/memchr2.valgrind: Likewise.
* lib/rawmemchr.valgrind: Likewise.
* lib/relocatable.valgrind: Likewise.
* lib/strchrnul.valgrind: Likewise.
Diffstat (limited to 'lib/memchr2.valgrind')
| -rw-r--r-- | lib/memchr2.valgrind | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/lib/memchr2.valgrind b/lib/memchr2.valgrind index 778fe867dc..ecda84e1f8 100644 --- a/lib/memchr2.valgrind +++ b/lib/memchr2.valgrind @@ -1,4 +1,20 @@ # Suppress a valgrind message about use of uninitialized memory in memchr2(). + +# Copyright (C) 2009-2019 Free Software Foundation, Inc. +# +# This program is free software: you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <https://www.gnu.org/licenses/>. + # Like memchr, it is safe to overestimate the length when the terminator # is guaranteed to be found. In this case, we may end up reading a word # that is partially uninitialized, but this use is OK for a speedup. |