public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34773] [4.3 regression] miscompilation of vfprintf_r
Date: Tue, 29 Jan 2008 06:31:00 -0000 [thread overview]
Message-ID: <20080129053950.28134.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34773-507@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from hp at gcc dot gnu dot org 2008-01-29 05:39 -------
I'm learning; first time around this new df and cfglayout stuff. I haven't
stumbled on anything anywhere actually explicitly saying so, but the "fake"
fallthrough edges are apparently the main part of cfglayout; better to pretend
all bb can fall through wherever they need to go than having unconditional
branches. It may be that not all parts of gcc agree on this, but I'm now
following the hypothesis that it's not as such the cause of this bug. The wrong
code (the correct code disappears) after the final "cleanup_cfg (0)" call of
fwprop1.
The original title may have been right.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34773
next prev parent reply other threads:[~2008-01-29 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 18:51 [Bug rtl-optimization/34773] New: fwprop1 bug causing " hp at gcc dot gnu dot org
2008-01-13 18:51 ` [Bug rtl-optimization/34773] " hp at gcc dot gnu dot org
2008-01-13 19:20 ` hp at gcc dot gnu dot org
2008-01-13 19:21 ` hp at gcc dot gnu dot org
2008-01-13 21:07 ` rguenth at gcc dot gnu dot org
2008-01-14 9:34 ` hp at gcc dot gnu dot org
2008-01-26 22:59 ` [Bug rtl-optimization/34773] [4.3 regression] " hp at gcc dot gnu dot org
2008-01-29 6:31 ` hp at gcc dot gnu dot org [this message]
2008-01-31 6:38 ` hp at gcc dot gnu dot org
2008-01-31 10:56 ` [Bug rtl-optimization/34773] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-02-01 21:29 ` hp at gcc dot gnu dot org
2008-02-01 21:30 ` hp at gcc dot gnu dot org
2008-02-01 21:31 ` hp at gcc dot gnu dot 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=20080129053950.28134.qmail@sourceware.org \
--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).