public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: Stefan Ring <stefanrin@gmail.com>, 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 18:05:39 +0100	[thread overview]
Message-ID: <f9e0c1c0-7a8b-2b63-eab4-ec0c7eb1b56c@hesbynett.no> (raw)
In-Reply-To: <CAAxjCEwaUQ8bGd7NYqTjVL=VN4PbRsXx7PvJJWLwd9SL9oZ1RQ@mail.gmail.com>

On 21/12/2021 17:05, Stefan Ring via Gcc-help wrote:
> 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.
> 

The operand of a sizeof expression is not evaluated (unless it is a
VLA).  So there is no problem with the "member1 = malloc(sizeof
*member1);" lines.  (Which is fortunate, because it is a very common idiom!)

I think the next step would be to start pulling in some of the
definitions for the various macros here, and then trying to reduce the
code further to get a smaller test case.

  parent reply	other threads:[~2021-12-21 17: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
2021-12-21 16:13   ` Adrian Moreno
2021-12-21 16:39     ` Segher Boessenkool
2021-12-21 17:05   ` David Brown [this message]
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=f9e0c1c0-7a8b-2b63-eab4-ec0c7eb1b56c@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=amorenoz@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=stefanrin@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).