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/112495] [11/12/13 Regression] ICE: verify_gimple failed (after vectorizer) with named address space (__seg_gs ) Date: Tue, 06 Feb 2024 13:20:10 +0000 [thread overview] Message-ID: <bug-112495-4-AWctyWhywI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112495-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112495 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:e22e3ee80f6b83d1f7a7d92be3c3d3f16e56fa17 commit r13-8289-ge22e3ee80f6b83d1f7a7d92be3c3d3f16e56fa17 Author: Richard Biener <rguenther@suse.de> Date: Mon Nov 13 10:20:37 2023 +0100 tree-optimization/112495 - alias versioning and address spaces We are not correctly handling differing address spaces in dependence analysis runtime alias check generation so refuse to do that. PR tree-optimization/112495 * tree-data-ref.cc (runtime_alias_check_p): Reject checks between different address spaces. * gcc.target/i386/pr112495.c: New testcase. (cherry picked from commit 0f593c0521caab8cfac53514b1a5e7d0d0dd1932)
next prev parent reply other threads:[~2024-02-06 13:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-12 14:32 [Bug c/112495] New: GCC: 14: internal compiler error: verify_gimple failed 141242068 at smail dot nju.edu.cn 2023-11-12 14:34 ` [Bug c/112495] " 141242068 at smail dot nju.edu.cn 2023-11-12 16:13 ` [Bug tree-optimization/112495] [11/12/13/14 Regression] internal compiler error: verify_gimple failed with named address space (__seg_gs ) pinskia at gcc dot gnu.org 2023-11-12 16:16 ` pinskia at gcc dot gnu.org 2023-11-13 9:18 ` [Bug tree-optimization/112495] [11/12/13/14 Regression] ICE: verify_gimple failed (after vectorizer) " rguenth at gcc dot gnu.org 2023-11-13 14:01 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:10 ` [Bug tree-optimization/112495] [11/12/13 " rguenth at gcc dot gnu.org 2024-02-06 13:20 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-17 11:12 ` [Bug tree-optimization/112495] [11/12 " cvs-commit at gcc dot gnu.org 2024-06-21 9:22 ` [Bug tree-optimization/112495] [11 " cvs-commit at gcc dot gnu.org 2024-06-21 9:37 ` rguenth 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-112495-4-AWctyWhywI@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).