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 tree-optimization/112307] Segmentation fault with -O1 -fcode-hoisting
Date: Tue, 31 Oct 2023 10:43:13 +0000	[thread overview]
Message-ID: <bug-112307-4-wurDCKRMdL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112307-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112307

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=109945

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
The transform in main is because we do

Value numbering stmt = _22 = &MEM <struct EnumeratorRange> [(void
*)&intersections + 1B] == _34;
Applying pattern match.pd:6940, gimple-match-5.cc:1815
Match-and-simplified &MEM <struct EnumeratorRange> [(void *)&intersections +
1B] == _34 to 0
RHS &MEM <struct EnumeratorRange> [(void *)&intersections + 1B] == _34
simplified to 0
Setting value number of _22 to 0 (changed)
Value numbering stmt = intersections.end_reached_ = _22;
No store match
Value numbering store intersections.end_reached_ to 0
Setting value number of .MEM_93 to .MEM_93 (changed)
Value numbering stmt = if (&MEM <struct EnumeratorRange> [(void
*)&intersections + 1B] == _34)
marking known outgoing edge 12 -> 15 executable

and that's using

/* Simplify pointer equality compares using PTA.  */
(for neeq (ne eq)
 (simplify
  (neeq @0 @1)
  (if (POINTER_TYPE_P (TREE_TYPE (@0))
       && ptrs_compare_unequal (@0, @1))
   { constant_boolean_node (neeq != EQ_EXPR, type); })))

which makes it really a similar issue as PR109945 - _34 points to
nonlocal/escaped but 'intersections' isn't part of that set though it
probably "escapes" at

<bb 2> [local count: 118111600]:
intersections = CompositeMesh::Intersections (&mesh); [return slot
optimization]

-fno-tree-pta is a (quite heavy) workaround.

  parent reply	other threads:[~2023-10-31 10:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  9:39 [Bug c++/112307] New: " raffael at casagrande dot ch
2023-10-31  9:51 ` [Bug tree-optimization/112307] " rguenth at gcc dot gnu.org
2023-10-31 10:21 ` rguenth at gcc dot gnu.org
2023-10-31 10:43 ` rguenth at gcc dot gnu.org [this message]
2024-03-05 11:34 ` rguenth at gcc dot gnu.org
2024-03-05 15:05 ` redi at gcc dot gnu.org
2024-03-05 15:37 ` rguenth at gcc dot gnu.org
2024-03-08 12:58 ` raffael at casagrande dot ch
2024-03-08 14:30 ` redi at gcc dot gnu.org
2024-03-08 14:32 ` redi at gcc dot gnu.org
2024-03-08 15:12 ` raffael at casagrande dot ch

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-112307-4-wurDCKRMdL@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).