public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/95174] [D] Incorrect compiled functions involving const fixed size arrays
Date: Tue, 19 May 2020 03:10:39 +0000 [thread overview]
Message-ID: <bug-95174-4-2Mf0eh6QuG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95174-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95174
--- Comment #3 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Witold Baryluk from comment #2)
> Doh. Of course. My bad. Sorry.
>
>
> static arrays are value type, dynamic arrays are reference type.
>
Dynamic arrays are still value types, the value passed around is a pointer and
length. For example:
void f(immutable(float[64]) x, float[] o) {
o[] = x[] * 2.0f;
}
float[64] x = 1.0f;
float[] o;
f(x, o);
// o does not change here.
assert(o.length == 0);
assert(o.ptr is null);
prev parent reply other threads:[~2020-05-19 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 12:07 [Bug d/95174] New: " witold.baryluk+gcc at gmail dot com
2020-05-18 14:12 ` [Bug d/95174] " ibuclaw at gdcproject dot org
2020-05-19 1:02 ` witold.baryluk+gcc at gmail dot com
2020-05-19 3:10 ` ibuclaw at gdcproject dot org [this message]
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-95174-4-2Mf0eh6QuG@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).