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 tree-optimization/36100] [4.4 Regression] always_inline attribute is broken at -O0
Date: Wed, 07 May 2008 16:56:00 -0000 [thread overview]
Message-ID: <20080507165548.8167.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36100-682@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from hp at gcc dot gnu dot org 2008-05-07 16:55 -------
This is not resolved. I still see
FAIL: g++.dg/tree-ssa/pr19637.C scan-tree-dump-times dom1 "return 1;" 3
for cris-elf and it's been a few days.
I'm reopening this PR to properly track progress.
--
hp at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36100
next prev parent reply other threads:[~2008-05-07 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 16:40 [Bug tree-optimization/36100] New: " hjl dot tools at gmail dot com
2008-05-01 18:58 ` [Bug tree-optimization/36100] " hjl dot tools at gmail dot com
2008-05-01 19:33 ` hjl dot tools at gmail dot com
2008-05-02 11:09 ` hubicka at gcc dot gnu dot org
2008-05-02 11:12 ` hubicka at ucw dot cz
2008-05-02 13:00 ` hjl dot tools at gmail dot com
2008-05-02 21:45 ` hubicka at ucw dot cz
2008-05-02 21:50 ` hjl dot tools at gmail dot com
2008-05-02 22:00 ` hubicka at ucw dot cz
2008-05-04 15:36 ` hjl dot tools at gmail dot com
2008-05-05 4:52 ` pinskia at gcc dot gnu dot org
2008-05-05 6:15 ` pinskia at gcc dot gnu dot org
2008-05-07 16:56 ` hp at gcc dot gnu dot org [this message]
2008-05-07 17:03 ` 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=20080507165548.8167.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).