From: Eric Botcazou <botcazou@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix bogus -Wstringop-overflow warning in Ada
Date: Thu, 18 Aug 2022 16:47:28 +0200 [thread overview]
Message-ID: <3120260.5fSG56mABF@arcturus> (raw)
In-Reply-To: <CAFiYyc32dW4qadKR-3xXC36SVtiDGs3xgr8Bp6fQP5-uhtVSOQ@mail.gmail.com>
> Hmm :/ But that means we _should_ force a sign extension but only
> from ptrofftype_p ()? That is, your test above should maybe read
>
> signop sgn = TYPE_SIGN (type);
> if (ptrofftype_p (type))
> sgn = SIGNED;
>
> assuming 'type' is the type of lowbnd
Yes, that's essentially equivalent to what get_offset_range does, but I'm not
sure why having two slightly different ways of doing it would be better than a
single one here, Maybe replace the call to get_precision in both places with
TYPE_PRECSION (type) then?
--
Eric Botcazou
next prev parent reply other threads:[~2022-08-18 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 13:56 Eric Botcazou
2022-08-17 11:27 ` Richard Biener
2022-08-17 13:38 ` Eric Botcazou
2022-08-18 7:30 ` Richard Biener
2022-08-18 7:55 ` Eric Botcazou
2022-08-18 9:22 ` Richard Biener
2022-08-18 14:47 ` Eric Botcazou [this message]
2022-08-19 7:30 ` Richard Biener
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=3120260.5fSG56mABF@arcturus \
--to=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).