public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109982] csmith: x86_64: znver1 issues
Date: Tue, 30 May 2023 07:23:06 +0000 [thread overview]
Message-ID: <bug-109982-4-6pGO7VAxko@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109982-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109982
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #11)
> (In reply to H.J. Lu from comment #9)
> > [hjl@gnu-cfl-3 pr109982]$ cat x.c
> > struct S0 {
> > long long int f0;
> > } __attribute__((aligned(128)));
> >
> > int padding = 1;
> > static struct S0 g_2415 __attribute__((aligned(4))) = {-1L};
> > static struct S0 *g_2500 __attribute__((visibility("internal"), used)) =
> > &g_2415;
> >
>
> I think the code is invalid since g_2500 isn't pointed to properly aligned
> data.
Yes, don't we diagnose this now?
next prev parent reply other threads:[~2023-05-30 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 8:15 [Bug target/109982] New: " dcb314 at hotmail dot com
2023-05-26 10:01 ` [Bug target/109982] " ubizjak at gmail dot com
2023-05-26 10:04 ` ubizjak at gmail dot com
2023-05-26 15:38 ` ubizjak at gmail dot com
2023-05-26 16:26 ` dcb314 at hotmail dot com
2023-05-26 16:41 ` dcb314 at hotmail dot com
2023-05-26 16:47 ` dcb314 at hotmail dot com
2023-05-26 17:24 ` dcb314 at hotmail dot com
2023-05-26 17:53 ` amonakov at gcc dot gnu.org
2023-05-26 20:28 ` hjl.tools at gmail dot com
2023-05-26 20:32 ` hjl.tools at gmail dot com
2023-05-26 20:37 ` hjl.tools at gmail dot com
2023-05-30 7:23 ` rguenth at gcc dot gnu.org [this message]
2023-05-30 7:45 ` amonakov at gcc dot gnu.org
2023-05-30 7:57 ` dcb314 at hotmail dot com
2023-05-30 8:50 ` amonakov at gcc dot gnu.org
2023-05-30 8:55 ` jakub 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-109982-4-6pGO7VAxko@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).