public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/108931] New: conditional operator for variably modified types
Date: Sat, 25 Feb 2023 12:38:46 +0000	[thread overview]
Message-ID: <bug-108931-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108931

            Bug ID: 108931
           Summary: conditional operator for variably modified types
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: muecker at gwdg dot de
  Target Milestone: ---

Created attachment 54536
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54536&action=edit
patch against trunk

For conditional operators with size expressions in both branches, the behavior
is erratic. While this seems to be undefined behavior (although it shouldn't
be), it is surprising and my cause subtle bugs, e.g. when using such casts or
statement expressions in macros. Also it seems easy to fix by always evaluating
the size of the active branch only and taking this size for the result.

For example, in some cases size expressions from both branches are evaluated:

int foo(void)
{
    return sizeof(*(0 ? (char(*)[f()])0 
                : (char(*)[g()])0));
}

foo:
        sub     rsp, 8
        call    g
        call    f
        add     rsp, 8
        ret

In other cases size from an unevaluated branch is taken as the result:

https://godbolt.org/z/o74e7T16x

                 reply	other threads:[~2023-02-25 12:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-108931-4@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).