From: Richard Biener <richard.guenther@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: analyzer/strndup-1.c: skip on *-*-vxworks*
Date: Tue, 29 Mar 2022 09:13:50 +0200 [thread overview]
Message-ID: <CAFiYyc32GRkrR3qjiGW3=B4oJ5LvtM5G01Qkm1B3nCkvpO+WTA@mail.gmail.com> (raw)
In-Reply-To: <orr16llco0.fsf@lxoliva.fsfla.org>
On Tue, Mar 29, 2022 at 4:24 AM Alexandre Oliva via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
>
> Add vxworks to the set of operating systems whose C libraries don't
> support strndup.
>
> Tested on affected systems and on x86_64-linux-gnu. Ok to install?
OK
>
> for gcc/testsuite/ChangeLog
>
> * gcc.dg/analyzer/strndup-1.c: Add *-*-vxworks* to no-strndup
> in libc.
> ---
> gcc/testsuite/gcc.dg/analyzer/strndup-1.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.dg/analyzer/strndup-1.c b/gcc/testsuite/gcc.dg/analyzer/strndup-1.c
> index edf494ac28448..8cf7a42bf5361 100644
> --- a/gcc/testsuite/gcc.dg/analyzer/strndup-1.c
> +++ b/gcc/testsuite/gcc.dg/analyzer/strndup-1.c
> @@ -1,4 +1,5 @@
> -/* { dg-skip-if "no strndup in libc" { *-*-darwin[789]* *-*-darwin10* *-*-mingw* } } */
> +/* { dg-skip-if "no strndup in libc" { *-*-darwin[789]* *-*-darwin10* *-*-mingw* *-*-vxworks* } } */
> +
> #include <string.h>
> #include <stdlib.h>
>
>
>
> --
> Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
> Free Software Activist GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts. Ask me about <https://stallmansupport.org>
prev parent reply other threads:[~2022-03-29 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 2:23 Alexandre Oliva
2022-03-29 7:13 ` Richard Biener [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFiYyc32GRkrR3qjiGW3=B4oJ5LvtM5G01Qkm1B3nCkvpO+WTA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=oliva@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).