public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/clang] string: Disable function_overload test on clang Date: Thu, 21 Dec 2023 19:00:26 +0000 (GMT) [thread overview] Message-ID: <20231221190026.C34BF386189D@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a529917387fec197cb70c0c20ff2f199298b3e94 commit a529917387fec197cb70c0c20ff2f199298b3e94 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Thu Jul 27 16:17:28 2023 -0300 string: Disable function_overload test on clang The test generates an ICE with clang 18.0. Diff: --- sysdeps/x86/tst-strncmp-rtm.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sysdeps/x86/tst-strncmp-rtm.c b/sysdeps/x86/tst-strncmp-rtm.c index af80f2ca76..9312bb879b 100644 --- a/sysdeps/x86/tst-strncmp-rtm.c +++ b/sysdeps/x86/tst-strncmp-rtm.c @@ -62,6 +62,7 @@ function (void) return 1; } +#ifndef __clang__ __attribute__ ((noinline)) __attribute_noclone__ static int function_overflow (void) @@ -71,6 +72,7 @@ function_overflow (void) else return 1; } +#endif __attribute__ ((noinline, noclone)) static int @@ -88,9 +90,11 @@ do_test (void) int status = do_test_1 (TEST_NAME, LOOP, prepare, function); if (status != EXIT_SUCCESS) return status; +#ifndef __clang__ status = do_test_1 (TEST_NAME, LOOP, prepare, function_overflow); if (status != EXIT_SUCCESS) return status; +#endif status = do_test_1 (TEST_NAME, LOOP, prepare, function_overflow2); if (status != EXIT_SUCCESS) return status;
next reply other threads:[~2023-12-21 19:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-21 19:00 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-01-29 18:03 Adhemerval Zanella 2023-09-28 17:58 Adhemerval Zanella 2023-08-30 12:43 Adhemerval Zanella
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=20231221190026.C34BF386189D@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /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: linkBe 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).