public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114912] [15 regression] SIGBUS in wi::copy<> on SPARC since r15-88-gc60b3e211c5557 since char array is not aligned to what it needs to be Date: Thu, 09 May 2024 05:04:03 +0000 [thread overview] Message-ID: <bug-114912-4-f5KEcQLkM5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114912 --- Comment #17 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:d7ff8ae5313bea755f5960786b33a7b151e7b663 commit r15-336-gd7ff8ae5313bea755f5960786b33a7b151e7b663 Author: Aldy Hernandez <aldyh@redhat.com> Date: Fri May 3 11:17:32 2024 +0200 [ranger] Force buffer alignment in Value_Range [PR114912] gcc/ChangeLog: PR tree-optimization/114912 * value-range.h (class Value_Range): Use a union.
next prev parent reply other threads:[~2024-05-09 5:04 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-01 19:12 [Bug middle-end/114912] New: [15 regression] SIGBUS in wi::copy<> on SPARC ro at gcc dot gnu.org 2024-05-01 19:12 ` [Bug middle-end/114912] " ro at gcc dot gnu.org 2024-05-01 22:36 ` aldyh at gcc dot gnu.org 2024-05-01 22:38 ` pinskia at gcc dot gnu.org 2024-05-02 5:26 ` ro at gcc dot gnu.org 2024-05-02 5:28 ` ro at gcc dot gnu.org 2024-05-02 5:29 ` pinskia at gcc dot gnu.org 2024-05-02 5:41 ` pinskia at gcc dot gnu.org 2024-05-02 8:47 ` [Bug middle-end/114912] [15 regression] SIGBUS in wi::copy<> on SPARC since r15-88-gc60b3e211c5557 pinskia at gcc dot gnu.org 2024-05-02 8:51 ` pinskia at gcc dot gnu.org 2024-05-02 11:16 ` [Bug tree-optimization/114912] [15 regression] SIGBUS in wi::copy<> on SPARC since r15-88-gc60b3e211c5557 since char array is not aligned to what it needs to be rguenth at gcc dot gnu.org 2024-05-02 20:44 ` pinskia at gcc dot gnu.org 2024-05-02 20:51 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-03 9:08 ` aldyh at gcc dot gnu.org 2024-05-08 17:05 ` aldyh at gcc dot gnu.org 2024-05-08 17:14 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-08 20:39 ` aldyh at gcc dot gnu.org 2024-05-08 20:40 ` aldyh at gcc dot gnu.org 2024-05-09 5:04 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-09 9:54 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-09 10:02 ` aldyh 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-114912-4-f5KEcQLkM5@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).