From: Stefan Ring <stefanrin@gmail.com>
To: Adrian Moreno <amorenoz@redhat.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: broken code only when optimized "-O2"
Date: Tue, 21 Dec 2021 17:05:44 +0100 [thread overview]
Message-ID: <CAAxjCEwaUQ8bGd7NYqTjVL=VN4PbRsXx7PvJJWLwd9SL9oZ1RQ@mail.gmail.com> (raw)
In-Reply-To: <cc01d4b4-ab21-febe-2ae4-197cfdca1816@redhat.com>
On Tue, Dec 21, 2021 at 4:40 PM Adrian Moreno via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> I'd really appreciate any hint or idea to try to understand this problem.
I guess the compiler doesn't like the dereferencing of uninitialized
pointers (in the sizeof expressions). I am not 100% sure that this
counts as dereferencing, but I would assume so. Because of this the
compiler will be free to behave however it likes to.
next prev parent reply other threads:[~2021-12-21 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 15:40 Adrian Moreno
2021-12-21 16:05 ` Stefan Ring [this message]
2021-12-21 16:13 ` Adrian Moreno
2021-12-21 16:39 ` Segher Boessenkool
2021-12-21 17:05 ` David Brown
2021-12-22 9:24 ` Adrian Moreno
2021-12-22 10:27 ` Florian Weimer
2021-12-22 10:34 ` Adrian Moreno
2021-12-22 10:36 ` Xi Ruoyao
2021-12-22 16:05 ` Adrian Moreno
2021-12-22 15:32 ` LIU Hao
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='CAAxjCEwaUQ8bGd7NYqTjVL=VN4PbRsXx7PvJJWLwd9SL9oZ1RQ@mail.gmail.com' \
--to=stefanrin@gmail.com \
--cc=amorenoz@redhat.com \
--cc=gcc-help@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).