public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "izamyatin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53128] [4.8 Regression] Compiler produces infinite loop on regular O2
Date: Thu, 03 May 2012 11:10:00 -0000	[thread overview]
Message-ID: <bug-53128-4-XY1Mdq8nKN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53128-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Igor Zamyatin <izamyatin at gmail dot com> 2012-05-03 11:09:15 UTC ---
Isn't it too aggressive from user perspective to perform such transformation
even without warning? Especially for the case when that "wrong" read is not
used later.
Sure it is dangerous anyway to make such access but at he same time it seems
this could affect lot of existing code...


  parent reply	other threads:[~2012-05-03 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 15:35 [Bug tree-optimization/53128] New: " izamyatin at gmail dot com
2012-04-26 15:58 ` [Bug tree-optimization/53128] " hjl.tools at gmail dot com
2012-04-26 16:21 ` amonakov at gcc dot gnu.org
2012-04-27  8:03 ` rguenther at suse dot de
2012-05-03 11:10 ` izamyatin at gmail dot com [this message]
2012-05-03 16:03 ` manu at gcc dot gnu.org
2012-05-04 13:19 ` izamyatin at gmail dot com
2012-05-04 16:16 ` manu at gcc dot gnu.org
2012-05-07  8:52 ` rguenther at suse dot de
2012-05-07 14:11 ` amonakov 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-53128-4-XY1Mdq8nKN@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).