public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108695] [13 Regression] Wrong code since r13-5215-gb1f30bf42d8d47 for dd_rescue package
Date: Wed, 08 Feb 2023 11:29:13 +0000 [thread overview]
Message-ID: <bug-108695-4-evoQAQJAX0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108695-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108695
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #6)
> Yes, I'm also suspecting this code and I can verify that using optimize("O0")
> for rijndaelEncrypt fixes the issue.
>
> The thing below is cast from 'const u8 *' and I thought it's valid to case
> to 'u32 *' and then access it. Can you explain to me how exactly the
> violation happens?
A cast is fine, what matters are the accesses. If the object has u32 type,
then casting
its address to const u8 * and later on back to u32 * and accessing through that
type
is fine, but if it has an incompatible type, it is not. Similarly, if it is
heap allocated, the type is given to it through the stores to it and later
reads from it should be done with a compatible (aliasing wise) type.
See section 6.5 in e.g. C17 for the details (definition of effective type and
the aliasing requirements).
next prev parent reply other threads:[~2023-02-08 11:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 12:56 [Bug ipa/108695] New: " marxin at gcc dot gnu.org
2023-02-07 12:56 ` [Bug ipa/108695] " marxin at gcc dot gnu.org
2023-02-07 15:17 ` pinskia at gcc dot gnu.org
2023-02-07 15:18 ` pinskia at gcc dot gnu.org
2023-02-08 7:24 ` marxin at gcc dot gnu.org
2023-02-08 7:25 ` marxin at gcc dot gnu.org
2023-02-08 7:38 ` pinskia at gcc dot gnu.org
2023-02-08 11:16 ` marxin at gcc dot gnu.org
2023-02-08 11:29 ` jakub at gcc dot gnu.org [this message]
2023-02-08 14:50 ` marxin at gcc dot gnu.org
2023-02-08 15:09 ` marxin at gcc dot gnu.org
2023-02-08 15:18 ` marxin at gcc dot gnu.org
2023-02-08 15:24 ` sam at gentoo dot org
2023-02-08 15:25 ` marxin at gcc dot gnu.org
2023-02-08 15:27 ` marxin at gcc dot gnu.org
2023-02-08 15:28 ` jakub at gcc dot gnu.org
2023-02-08 15:52 ` marxin at gcc dot gnu.org
2023-02-23 21:04 ` kurt at garloff dot de
2023-02-23 22:04 ` kurt at garloff dot de
2023-02-24 12:24 ` kurt at garloff dot de
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=bug-108695-4-evoQAQJAX0@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).