From: Dimitar Dimitrov <dimitar@dinux.eu>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: mallign: Handle word size of 1 byte
Date: Mon, 16 May 2022 20:18:53 +0300 [thread overview]
Message-ID: <YoKHfZvaJsgHRW2k@kendros> (raw)
In-Reply-To: <20220508073104.1698197-2-dimitar@dinux.eu>
On Sun, May 08, 2022 at 10:31:04AM +0300, Dimitar Dimitrov wrote:
> This patch fixes a spurious warning for pru-unknown-elf target:
> gcc/testsuite/gcc.dg/mallign.c:12:27: warning: ignoring return value of 'malloc' declared with attribute 'warn_unused_result' [-Wunused-result]
>
> For 8-bit targets the resulting mask ignores all bits in the value
> returned by malloc. Fix by first checking the target word size.
>
> Sanity checked that there are no new failures on x86_64-pc-linux-gnu.
>
> Ok for trunk?
Ping. Does this count as an obvious fix?
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/mallign.c: Skip check if sizeof(word)==1.
>
> Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
> ---
> gcc/testsuite/gcc.dg/mallign.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.dg/mallign.c b/gcc/testsuite/gcc.dg/mallign.c
> index 349cdaa343f..9a18a00c3b0 100644
> --- a/gcc/testsuite/gcc.dg/mallign.c
> +++ b/gcc/testsuite/gcc.dg/mallign.c
> @@ -9,7 +9,7 @@ typedef int word __attribute__((mode(word)));
>
> int main()
> {
> - if ((__UINTPTR_TYPE__)malloc (1) & (sizeof(word)-1))
> + if ((sizeof(word)>1) && ((__UINTPTR_TYPE__)malloc (1) & (sizeof(word)-1)))
> abort ();
> return 0;
> }
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-05-16 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 7:31 Dimitar Dimitrov
2022-05-16 17:18 ` Dimitar Dimitrov [this message]
2022-05-23 8:04 ` Richard Sandiford
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=YoKHfZvaJsgHRW2k@kendros \
--to=dimitar@dinux.eu \
--cc=gcc-patches@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).