public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/17742] [4.0 Regression] C Optimization error with -O1 on i686
Date: Thu, 11 Nov 2004 20:13:00 -0000 [thread overview]
Message-ID: <20041111201300.27069.qmail@sourceware.org> (raw)
In-Reply-To: <20040929223724.17742.m.calderbank@iname.com>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-11-11 20:12 -------
Subject: Bug 17742
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: rakdver@gcc.gnu.org 2004-11-11 20:12:36
Modified files:
gcc : ChangeLog tree-scalar-evolution.c
Log message:
PR tree-optimization/17742
* tree-scalar-evolution.c (follow_ssa_edge_in_rhs): Handle
MINUS_EXPR correctly.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.6279&r2=2.6280
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-scalar-evolution.c.diff?cvsroot=gcc&r1=2.11&r2=2.12
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17742
next prev parent reply other threads:[~2004-11-11 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 22:37 [Bug tree-optimization/17742] New: C Optimization error with -O1 and -O2 " m dot calderbank at iname dot com
2004-09-29 22:46 ` [Bug tree-optimization/17742] [4.0 Regression] C Optimization error with -O1 " pinskia at gcc dot gnu dot org
2004-09-30 21:46 ` pinskia at gcc dot gnu dot org
2004-10-01 0:21 ` m dot calderbank at iname dot com
2004-11-08 23:20 ` reichelt at gcc dot gnu dot org
2004-11-08 23:25 ` pinskia at gcc dot gnu dot org
2004-11-08 23:38 ` reichelt at gcc dot gnu dot org
2004-11-09 0:15 ` rakdver at gcc dot gnu dot org
2004-11-09 11:47 ` rakdver at gcc dot gnu dot org
2004-11-11 20:13 ` cvs-commit at gcc dot gnu dot org [this message]
2004-11-11 20:14 ` rakdver 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=20041111201300.27069.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).