public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug d/104538] New: gdc/d21: segfault on mips64
@ 2022-02-15  3:46 syq at debian dot org
  2022-02-15  3:48 ` [Bug d/104538] " syq at debian dot org
  2022-03-09 10:30 ` ibuclaw at gdcproject dot org
  0 siblings, 2 replies; 3+ messages in thread
From: syq at debian dot org @ 2022-02-15  3:46 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 104538
           Summary: gdc/d21: segfault on mips64
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: syq at debian dot org
  Target Milestone: ---

https://buildd.debian.org/status/fetch.php?pkg=gcc-12&arch=mips64el&ver=12-20220214-1&stamp=1644848228&raw=0


The segment is from:
gcc/d/dmd/ctfeexpr.d:
UnionExp changeArrayLiteralLength(const ref Loc loc, TypeArray arrayType,
Expression oldval, size_t oldlen, size_t newlen) 


        if (oldlen != 0)
        {
            assert(oldval.op == EXP.arrayLiteral);
            ArrayLiteralExp ae = cast(ArrayLiteralExp)oldval;
            foreach (size_t i; 0 .. copylen)
                (*elements)[i] = (*ae.elements)[indxlo + i];
        }
        if (elemType.ty == Tstruct || elemType.ty == Tsarray)
        {
            /* If it is an aggregate literal representing a value type,
             * we need to create a unique copy for each element
             */
            foreach (size_t i; copylen .. newlen)
                (*elements)[i] = copyLiteral(defaultElem).copy();
        }
        else
        {
            foreach (size_t i; copylen .. newlen)
                (*elements)[i] = defaultElem;
        }
>>>>    emplaceExp!(ArrayLiteralExp)(&ue, loc, arrayType, elements);
        ArrayLiteralExp aae = cast(ArrayLiteralExp)ue.exp();
        aae.ownedByCtfe = OwnedBy.ctfe;

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug d/104538] gdc/d21: segfault on mips64
  2022-02-15  3:46 [Bug d/104538] New: gdc/d21: segfault on mips64 syq at debian dot org
@ 2022-02-15  3:48 ` syq at debian dot org
  2022-03-09 10:30 ` ibuclaw at gdcproject dot org
  1 sibling, 0 replies; 3+ messages in thread
From: syq at debian dot org @ 2022-02-15  3:48 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from YunQiang Su <syq at debian dot org> ---
This problem happens only for the new gdc code introduced in gcc-12.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug d/104538] gdc/d21: segfault on mips64
  2022-02-15  3:46 [Bug d/104538] New: gdc/d21: segfault on mips64 syq at debian dot org
  2022-02-15  3:48 ` [Bug d/104538] " syq at debian dot org
@ 2022-03-09 10:30 ` ibuclaw at gdcproject dot org
  1 sibling, 0 replies; 3+ messages in thread
From: ibuclaw at gdcproject dot org @ 2022-03-09 10:30 UTC (permalink / raw)
  To: gcc-bugs

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

Iain Buclaw <ibuclaw at gdcproject dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Thanks, looking into this now.

Marking as duplicate of PR104835 though.

*** This bug has been marked as a duplicate of bug 104835 ***

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-03-09 10:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-15  3:46 [Bug d/104538] New: gdc/d21: segfault on mips64 syq at debian dot org
2022-02-15  3:48 ` [Bug d/104538] " syq at debian dot org
2022-03-09 10:30 ` ibuclaw at gdcproject dot org

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).