public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/110113] gdc -fpreview=dip1021 crash in d/dmd/root/aav.d:127 dmd_aaGetRvalue from DsymbolTable::lookup(Identifier const*)
Date: Wed, 07 Jun 2023 16:08:15 +0000	[thread overview]
Message-ID: <bug-110113-4-zqabAorGpr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110113-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from ibuclaw at gcc dot gnu.org ---
Same, but without any compiler errors.

This is reproducible in upstream dmd too.

dmd -lowmem -preview=dip1021 pr110113.d -o-

---
class LUBench { }
void lup(ulong , ulong , int , int = 1)
{
    new LUBench;
}
void lup_3200(ulong iters, ulong flops)
{
    lup(iters, flops, 3200);
}
void raytrace()
{
    struct V
    {
        float x, y, z;
        auto normalize() { }
        struct Tid { }
        auto spawnLinked() { }
        string[] namesByTid;
        class MessageBox { }
        auto cross() { }
    }
}

  parent reply	other threads:[~2023-06-07 16:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 16:42 [Bug d/110113] New: " witold.baryluk+gcc at gmail dot com
2023-06-04 16:44 ` [Bug d/110113] " witold.baryluk+gcc at gmail dot com
2023-06-04 16:45 ` witold.baryluk+gcc at gmail dot com
2023-06-06 20:37 ` ibuclaw at gcc dot gnu.org
2023-06-06 20:49 ` ibuclaw at gcc dot gnu.org
2023-06-06 22:01 ` ibuclaw at gcc dot gnu.org
2023-06-07 16:05 ` ibuclaw at gcc dot gnu.org
2023-06-07 16:08 ` ibuclaw at gcc dot gnu.org [this message]
2023-06-07 17:14 ` ibuclaw at gcc dot gnu.org
2023-06-10 17:31 ` ibuclaw at gcc dot gnu.org
2023-06-11 17:06 ` witold.baryluk+gcc at gmail dot com
2023-06-26  0:50 ` cvs-commit at gcc dot gnu.org
2023-06-26  0:51 ` cvs-commit at gcc dot gnu.org
2023-06-26  0:53 ` ibuclaw at gcc dot gnu.org

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