public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1
Date: Thu, 29 Jun 2023 09:17:45 +0000 [thread overview]
Message-ID: <bug-109780-4-MAGoRgG2SI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109780-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780
--- Comment #25 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Xi Ruoyao from comment #24)
> (In reply to H.J. Lu from comment #23)
> > Created attachment 55424 [details]
> > An updated patch
>
> Unfortunately Spidermonkey 115 still crashes even with the patch (and -O3
> -march=tigerlike -mtune=tigerlake -fno-exceptions). The problem seems an
> unaligned stack slot is assigned for an object of a 512-bit aligned class.
> Then the pointer to the object is passed to another function which stores
> into the object with 256-bit vmovdqu but the stack slot is only aligned to
> 128-bit in fact. I'll try to reduce.
Nope, it seems a bug in mozilla code.
next prev parent reply other threads:[~2023-06-29 9:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 20:35 [Bug c/109780] New: " dcb314 at hotmail dot com
2023-05-08 20:44 ` [Bug target/109780] " pinskia at gcc dot gnu.org
2023-05-08 20:49 ` pinskia at gcc dot gnu.org
2023-05-08 22:09 ` amonakov at gcc dot gnu.org
2023-05-09 7:41 ` rguenth at gcc dot gnu.org
2023-05-09 8:10 ` dcb314 at hotmail dot com
2023-05-09 10:00 ` dcb314 at hotmail dot com
2023-05-09 10:11 ` dcb314 at hotmail dot com
2023-05-09 10:44 ` dcb314 at hotmail dot com
2023-05-09 11:10 ` dcb314 at hotmail dot com
2023-05-09 11:32 ` marxin at gcc dot gnu.org
2023-05-09 11:56 ` amonakov at gcc dot gnu.org
2023-05-09 12:03 ` marxin at gcc dot gnu.org
2023-05-09 14:49 ` amonakov at gcc dot gnu.org
2023-05-09 14:57 ` [Bug target/109780] [12/13/14 Regression] " amonakov at gcc dot gnu.org
2023-06-23 9:42 ` rguenth at gcc dot gnu.org
2023-06-26 12:57 ` xry111 at gcc dot gnu.org
2023-06-27 18:45 ` xry111 at gcc dot gnu.org
2023-06-27 23:35 ` hjl.tools at gmail dot com
2023-06-28 9:48 ` xry111 at gcc dot gnu.org
2023-06-28 9:59 ` xry111 at gcc dot gnu.org
2023-06-28 15:47 ` hjl.tools at gmail dot com
2023-06-28 15:49 ` xry111 at gcc dot gnu.org
2023-06-28 21:39 ` xry111 at gcc dot gnu.org
2023-06-28 21:40 ` xry111 at gcc dot gnu.org
2023-06-29 2:43 ` hjl.tools at gmail dot com
2023-06-29 8:48 ` xry111 at gcc dot gnu.org
2023-06-29 9:17 ` xry111 at gcc dot gnu.org [this message]
2024-01-10 17:33 ` jamborm 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-109780-4-MAGoRgG2SI@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).