public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109982] New: csmith: x86_64: znver1 issues Date: Fri, 26 May 2023 08:15:03 +0000 [thread overview] Message-ID: <bug-109982-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109982 Bug ID: 109982 Summary: csmith: x86_64: znver1 issues Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 55164 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55164&action=edit C source code The attached C source code does this: $ ../results/bin/gcc -w bug923.c runData/keep/in.11.c: In function ‘func_68’: runData/keep/in.11.c:835:15: note: the ABI for passing parameters with 128-byte alignment has changed in GCC 4.6 $ ./a.out checksum = 4ED89677 $ ../results/bin/gcc -w -march=znver1 bug923.c runData/keep/in.11.c: In function ‘func_68’: runData/keep/in.11.c:835:15: note: the ABI for passing parameters with 128-byte alignment has changed in GCC 4.6 $ ./a.out Segmentation fault (core dumped) $ The bug first seems to appear sometime between snapshot 20221218 (git hash fd69977febf399d1992bbf8d66ae9170e0a4dc9f) and 20221225 (git hash febb58d28bfa4b544ec7ffec2d61f46d25205ff0).
next reply other threads:[~2023-05-26 8:15 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 8:15 dcb314 at hotmail dot com [this message] 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 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@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: linkBe 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).