public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57300] [4.8/4.9 Regression] statement in expression miscompiled at -O3 in 32-bit mode
Date: Thu, 16 May 2013 08:51:00 -0000	[thread overview]
Message-ID: <bug-57300-4-FxShmdf5D2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57300-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Steven Bosscher <steven at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> Not sure if it is safe to run df_analyze when the cfg is gone (split5
> pass)

Well, it doesn't crash but it's not correct. Without basic block
pointers on the insns, even the scan problem doesn't run properly
anymore.

One of the target machine reorgs does this, FWIW.


  parent reply	other threads:[~2013-05-16  8:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 19:41 [Bug rtl-optimization/57300] New: " dhazeghi at yahoo dot com
2013-05-16  7:53 ` [Bug rtl-optimization/57300] [4.8/4.9 Regression] " jakub at gcc dot gnu.org
2013-05-16  8:11 ` jakub at gcc dot gnu.org
2013-05-16  8:16 ` jakub at gcc dot gnu.org
2013-05-16  8:35 ` jakub at gcc dot gnu.org
2013-05-16  8:51 ` steven at gcc dot gnu.org [this message]
2013-05-16  9:02 ` jakub at gcc dot gnu.org
2013-05-16  9:29 ` ebotcazou at gcc dot gnu.org
2013-05-16  9:43 ` jakub at gcc dot gnu.org
2013-05-16  9:50 ` steven at gcc dot gnu.org
2013-05-16 10:08 ` jakub at gcc dot gnu.org
2013-05-16 10:13 ` jakub at gcc dot gnu.org
2013-05-16 11:26 ` rguenth at gcc dot gnu.org
2013-05-16 14:48 ` ebotcazou at gcc dot gnu.org
2013-05-20  7:13 ` jakub 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-57300-4-FxShmdf5D2@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).