public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c [not found] <bug-22366-280@http.gcc.gnu.org/bugzilla/> @ 2005-10-13 1:49 ` pinskia at gcc dot gnu dot org 2006-02-27 14:01 ` steven at gcc dot gnu dot org 2006-04-17 18:13 ` pinskia at gcc dot gnu dot org 2 siblings, 0 replies; 4+ messages in thread From: pinskia at gcc dot gnu dot org @ 2005-10-13 1:49 UTC (permalink / raw) To: gcc-bugs ------- Comment #7 from pinskia at gcc dot gnu dot org 2005-10-13 01:49 ------- 21513 is an issue which can be resolved when loop.c is removed as we don't need to store the profile info due to __builtin_expect in notes. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |21513 nThis| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22366 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c [not found] <bug-22366-280@http.gcc.gnu.org/bugzilla/> 2005-10-13 1:49 ` [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c pinskia at gcc dot gnu dot org @ 2006-02-27 14:01 ` steven at gcc dot gnu dot org 2006-04-17 18:13 ` pinskia at gcc dot gnu dot org 2 siblings, 0 replies; 4+ messages in thread From: steven at gcc dot gnu dot org @ 2006-02-27 14:01 UTC (permalink / raw) To: gcc-bugs ------- Comment #8 from steven at gcc dot gnu dot org 2006-02-27 14:01 ------- The old RTL loop optimizer is no more on the trunk, so there is no reason to keep this meta-bug open. -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22366 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c [not found] <bug-22366-280@http.gcc.gnu.org/bugzilla/> 2005-10-13 1:49 ` [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c pinskia at gcc dot gnu dot org 2006-02-27 14:01 ` steven at gcc dot gnu dot org @ 2006-04-17 18:13 ` pinskia at gcc dot gnu dot org 2 siblings, 0 replies; 4+ messages in thread From: pinskia at gcc dot gnu dot org @ 2006-04-17 18:13 UTC (permalink / raw) To: gcc-bugs -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.2.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22366 ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <bug-22366-4@http.gcc.gnu.org/bugzilla/>]
* [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c [not found] <bug-22366-4@http.gcc.gnu.org/bugzilla/> @ 2013-12-24 22:55 ` steven at gcc dot gnu.org 0 siblings, 0 replies; 4+ messages in thread From: steven at gcc dot gnu.org @ 2013-12-24 22:55 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22366 Bug 22366 depends on bug 19078, which changed state. Bug 19078 Summary: Poor quality code after loop unrolling. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19078 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |DUPLICATE ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-12-24 22:55 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-22366-280@http.gcc.gnu.org/bugzilla/>
2005-10-13 1:49 ` [Bug middle-end/22366] [meta-bug] issues related to the removal of loop.c pinskia at gcc dot gnu dot org
2006-02-27 14:01 ` steven at gcc dot gnu dot org
2006-04-17 18:13 ` pinskia at gcc dot gnu dot org
[not found] <bug-22366-4@http.gcc.gnu.org/bugzilla/>
2013-12-24 22:55 ` steven at gcc dot gnu.org
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).