public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6510] testsuite: Fix gcc.dg/analyzer/allocation-size-multiline-3.c
Date: Tue,  7 Mar 2023 00:15:05 +0000 (GMT)	[thread overview]
Message-ID: <20230307001505.CD1533858C66@sourceware.org> (raw)

https://gcc.gnu.org/g:1d92cd072ef4b2e4f309eefbcfe64c368d220f29

commit r13-6510-g1d92cd072ef4b2e4f309eefbcfe64c368d220f29
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Fri Feb 24 20:12:46 2023 +0100

    testsuite: Fix gcc.dg/analyzer/allocation-size-multiline-3.c
    
    For 32-bit newlib targets (such as cris-elf and pru-elf),
    that int32_t is "long int".  See other regexps in the
    testsuite matching "aka (long )?int" (with single-quotes
    where needed) where the pattern in
    allocation-size-multiline-3.c matches plain "int".  Uses the
    special syntax recently introduced for multi-line patterns.
    
    testsuite:
            * gcc.dg/analyzer/allocation-size-multiline-3.c: Handle
            int32_t being "long int".

Diff:
---
 gcc/testsuite/gcc.dg/analyzer/allocation-size-multiline-3.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/analyzer/allocation-size-multiline-3.c b/gcc/testsuite/gcc.dg/analyzer/allocation-size-multiline-3.c
index e27364a8e83..b3de582368f 100644
--- a/gcc/testsuite/gcc.dg/analyzer/allocation-size-multiline-3.c
+++ b/gcc/testsuite/gcc.dg/analyzer/allocation-size-multiline-3.c
@@ -21,7 +21,7 @@ void test_constant_99 (void)
     |                  ^~~~~~
     |                  |
     |                  (1) allocated 99 bytes here
-    |                  (2) assigned to 'int32_t *' {aka 'int *'} here; 'sizeof (int32_t {aka int})' is '4'
+    |                  (2) assigned to 'int32_t *' {aka '{re:long :re?}int *'} here; 'sizeof (int32_t {aka {re:long :re?}int})' is '4'
     |
    { dg-end-multiline-output "" } */
 
@@ -39,6 +39,6 @@ void test_symbolic (int n)
     |                  ^~~~~~
     |                  |
     |                  (1) allocated 'n * 2' bytes here
-    |                  (2) assigned to 'int32_t *' {aka 'int *'} here; 'sizeof (int32_t {aka int})' is '4'
+    |                  (2) assigned to 'int32_t *' {aka '{re:long :re?}int *'} here; 'sizeof (int32_t {aka {re:long :re?}int})' is '4'
     |
    { dg-end-multiline-output "" } */

                 reply	other threads:[~2023-03-07  0:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230307001505.CD1533858C66@sourceware.org \
    --to=hp@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).