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] malloc: Only enable -Waggressive-loop-optimizations suppression for gcc
Date: Fri, 29 Apr 2022 14:07:03 +0000 (GMT)	[thread overview]
Message-ID: <20220429140703.48F283856DDC@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7f3c63894ccb7bd0d8ec7d133f0c91fd93cb3ef8

commit 7f3c63894ccb7bd0d8ec7d133f0c91fd93cb3ef8
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Fri Mar 25 09:00:12 2022 -0300

    malloc: Only enable -Waggressive-loop-optimizations suppression for gcc

Diff:
---
 malloc/tst-dynarray.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/malloc/tst-dynarray.c b/malloc/tst-dynarray.c
index 51b99e2a5a..c3a0e925f9 100644
--- a/malloc/tst-dynarray.c
+++ b/malloc/tst-dynarray.c
@@ -482,7 +482,7 @@ test_long_overflow (void)
        iteration would invoke undefined behavior.  That loop iteration
        can never be executed because an allocation of this size must
        fail.  */
-    DIAG_IGNORE_NEEDS_COMMENT (12, "-Waggressive-loop-optimizations");
+    DIAG_IGNORE_NEEDS_COMMENT_GCC (12, "-Waggressive-loop-optimizations");
     TEST_VERIFY (!dynarray_long_resize
                  (&dyn, (SIZE_MAX / sizeof (long)) + 1));
     DIAG_POP_NEEDS_COMMENT;
@@ -499,7 +499,7 @@ test_long_overflow (void)
        iteration would invoke undefined behavior.  That loop iteration
        can never be executed because an allocation of this size must
        fail.  */
-    DIAG_IGNORE_NEEDS_COMMENT (12, "-Waggressive-loop-optimizations");
+    DIAG_IGNORE_NEEDS_COMMENT_GCC (12, "-Waggressive-loop-optimizations");
     TEST_VERIFY (!dynarray_long_noscratch_resize
                  (&dyn, (SIZE_MAX / sizeof (long)) + 1));
     DIAG_POP_NEEDS_COMMENT;


             reply	other threads:[~2022-04-29 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 14:07 Adhemerval Zanella [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-02 15:56 Adhemerval Zanella
2024-02-09 17:34 Adhemerval Zanella
2024-02-07 14:10 Adhemerval Zanella
2024-01-29 18:00 Adhemerval Zanella
2023-12-21 18:56 Adhemerval Zanella
2023-09-28 17:55 Adhemerval Zanella
2023-08-30 12:39 Adhemerval Zanella
2023-02-09 19:51 Adhemerval Zanella
2022-10-28 17:44 Adhemerval Zanella
2022-10-04 13:02 Adhemerval Zanella
2022-06-09 21:23 Adhemerval Zanella
2022-06-09 13:19 Adhemerval Zanella
2022-06-03 14:09 Adhemerval Zanella
2022-05-13 14:22 Adhemerval Zanella
2022-05-12 19:36 Adhemerval Zanella
2022-05-10 18:27 Adhemerval Zanella
2022-04-04 12:57 Adhemerval Zanella
2022-03-31 19:09 Adhemerval Zanella
2022-03-29 20:33 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=20220429140703.48F283856DDC@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: 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).