public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/104743] [12 regression] gdc.dg/torture/pr96152.d FAILs
Date: Wed, 02 Mar 2022 09:47:41 +0000	[thread overview]
Message-ID: <bug-104743-4-jw2Jdp2x28@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104743-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
> Does anything change if you compile the test with
> `-ftrivial-auto-var-init=zero` ?

No, the test fails just the same.

gdb shows

Thread 2 received signal SIGBUS, Bus error.
[Switching to Thread 1 (LWP 1)]
_d_newitemU (_ti=0xffffffff7f1f3000) at
/vol/gcc/src/hg/master/local/libphobos/libdruntime/rt/lifetime.d:1110
1110            *cast(TypeInfo*)(p + itemSize) = null; // the GC might not have
cleared this area
(gdb) bt
#0  _d_newitemU (_ti=0xffffffff7f1f3000) at
/vol/gcc/src/hg/master/local/libphobos/libdruntime/rt/lifetime.d:1110
#1  0x000000010007bd64 in rt.aaA.allocEntry(scope const(rt.aaA.Impl*), scope
const(void*)) (aa=0xffffffff7f1f2000, pkey=0xffffffff7f1f0000) at
/vol/gcc/src/hg/master/local/libphobos/libdruntime/rt/aaA.d:214
#2  0x000000010007cd14 in _d_assocarrayliteralTX (ti=0x100071db8 <initializer
for TypeInfo_HS7pr9615217__unittest_L20_C7FNfZ15ThrowingElementi>, keys=...,
vals=...) at /vol/gcc/src/hg/master/local/libphobos/libdruntime/rt/aaA.d:767
#3  0x000000010007b57c in
object.aaLiteral!(pr96152.__unittest_L20_C7().ThrowingElement,
int).aaLiteral(pr96152.__unittest_L20_C7().ThrowingElement[], int[]) (keys=...,
values=...) at /vol/gcc/src/hg/master/local/libphobos/libdruntime/object.d:2868
...
1: x/i $pc
=> 0x100087080 <_d_newitemU+100>:       clrx  [ %o0 + %i2 ]
(gdb) p/x $o0 + $i2
$3 = 0xffffffff7f1f0054

i.e. the address isn't properly 8-byte aligned as required on a
strict-alignment target like SPARC.

  parent reply	other threads:[~2022-03-02  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 13:20 [Bug d/104743] New: " ro at gcc dot gnu.org
2022-03-01 14:01 ` [Bug d/104743] " rguenth at gcc dot gnu.org
2022-03-01 21:45 ` ibuclaw at gdcproject dot org
2022-03-02  9:47 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-03-04 12:41 ` ibuclaw at gdcproject dot 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-104743-4-jw2Jdp2x28@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).