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:31:00 -0000	[thread overview]
Message-ID: <bug-58920-4-KqRg4YBQtK@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 #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #5)
> > As of pointer vs. reference types this shouldn't matter here as you
> > annotate actualy tcc_reference trees, not types.
> 
> What Andrew meant is that one can think that it would be valid to set the
> flag
> on tcc_reference trees if operand #0 has REFERENCE_TYPE instead of
> POINTER_TYPE,
> but of course that doesn't work because they can be smashed together.

Yeah, that can't be the way to distinguish them (though on GENERIC they
are not smashed together and the Frontend would do the TREE_THIS_NOTRAP
setting anyway).


  parent reply	other threads:[~2013-10-30 10:31 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
2013-10-30 10:27 ` ebotcazou at gcc dot gnu.org
2013-10-30 10:31 ` rguenth at gcc dot gnu.org [this message]
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-KqRg4YBQtK@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).