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/58920] Overeager optimization based on TREE_THIS_NOTRAP
Date: Wed, 30 Oct 2013 10:16:00 -0000	[thread overview]
Message-ID: <bug-58920-4-4TMGwx3NWy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58920-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58920

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #3)
> > The TREE_THIS_NOTRAP macro came up in email the other day, and it seemed to
> > me that it would be useful to set on C++ references, since they are required
> > to refer to objects; trying to read from a null reference gives undefined
> > behavior.  So I tried the attached patch.  But it breaks all the ext_pointer
> > tests in libstdc++.
> > 
> > Basically, what's happening is that there is a code path which is never
> > taken which leads to an explicit null dereference.  The optimizers see this
> > happening within a loop and decide to hoist it out of the loop.  So now it
> > is executed before the loop starts, and causes a SEGV.
> 
> If the dereference can generate a SEGV before being moved and nevertheless
> has the TREE_THIS_NOTRAP flag, then this is the bug and loop invariant
> motion does
> not make things worse.
> 
> As Andrew explained, you cannot set TREE_THIS_NOTRAP on all references.  In
> Ada,
> we set it only on parameters passed by reference, but it needs to be cleared
> during inlining because of this kind of issues.

"This kind of issues" is that GCC treats TREE_THIS_NOTRAP as applying
independent of the execution context.  That is, if you have

  if (p)
    *p = 0;

and mark *p with TREE_THIS_NOTRAP then GCC thinks *p will not trap
even when moved before the if (p) check.  So it has no concept of
"conditionally doesn't trap".

Though I thought that for C++ references that would be a non-issue.
As of pointer vs. reference types this shouldn't matter here as you
annotate actualy tcc_reference trees, not types.


  parent reply	other threads:[~2013-10-30 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  3:25 [Bug tree-optimization/58920] New: " jason at gcc dot gnu.org
2013-10-30  3:27 ` [Bug tree-optimization/58920] " jason at gcc dot gnu.org
2013-10-30  4:07 ` pinskia at gcc dot gnu.org
2013-10-30 10:04 ` ebotcazou at gcc dot gnu.org
2013-10-30 10:16 ` rguenth at gcc dot gnu.org [this message]
2013-10-30 10:27 ` ebotcazou at gcc dot gnu.org
2013-10-30 10:31 ` rguenth at gcc dot gnu.org
2021-08-13 23:42 ` pinskia 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-58920-4-4TMGwx3NWy@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).