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/21173] [4.0/4.1 regression] miscompiled pointer subtraction broke Linux kernel
Date: Mon, 25 Apr 2005 14:03:00 -0000 [thread overview]
Message-ID: <20050425140315.4828.qmail@sourceware.org> (raw)
In-Reply-To: <20050423092333.21173.mikpe@csd.uu.se>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-25 14:03 -------
Subject: Bug 21173
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-4_0-branch
Changes by: dberlin@gcc.gnu.org 2005-04-25 14:02:38
Modified files:
gcc : ChangeLog tree-ssa-pre.c
Log message:
2005-04-25 Daniel Berlin <dberlin@dberlin.org>
Fix PR tree-optimization/21173
* tree-ssa-pre.c (create_expression_by_pieces): Call unshare_expr
on things we pass to force_gimple_operand. Don't try to special
case min_invariants.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=2.7592.2.192&r2=2.7592.2.193
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-pre.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=2.65.4.2&r2=2.65.4.3
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21173
next prev parent reply other threads:[~2005-04-25 14:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 9:23 [Bug c/21173] New: " mikpe at csd dot uu dot se
2005-04-23 11:56 ` [Bug c/21173] " belyshev at depni dot sinp dot msu dot ru
2005-04-23 12:17 ` azarah at gentoo dot org
2005-04-23 12:30 ` [Bug tree-optimization/21173] [4.0 regression] " belyshev at depni dot sinp dot msu dot ru
2005-04-23 12:52 ` [Bug tree-optimization/21173] [4.0/4.1 " belyshev at depni dot sinp dot msu dot ru
2005-04-23 13:18 ` pinskia at gcc dot gnu dot org
2005-04-23 13:24 ` steven at gcc dot gnu dot org
2005-04-23 13:36 ` steven at gcc dot gnu dot org
2005-04-23 13:39 ` steven at gcc dot gnu dot org
2005-04-23 14:59 ` jakub at gcc dot gnu dot org
2005-04-23 15:09 ` dberlin at dberlin dot org
2005-04-23 15:13 ` dberlin at dberlin dot org
2005-04-23 17:19 ` azarah at gentoo dot org
2005-04-23 19:37 ` steven at gcc dot gnu dot org
2005-04-23 23:01 ` stevenb at suse dot de
2005-04-24 9:23 ` stevenb at suse dot de
2005-04-24 15:19 ` dberlin at gcc dot gnu dot org
2005-04-24 15:27 ` dberlin at dberlin dot org
2005-04-25 14:00 ` cvs-commit at gcc dot gnu dot org
2005-04-25 14:03 ` cvs-commit at gcc dot gnu dot org [this message]
2005-04-25 14:19 ` cvs-commit at gcc dot gnu dot org
2005-04-25 14:47 ` pinskia at gcc dot gnu dot org
2005-04-25 14:50 ` jakub at gcc dot gnu dot org
2005-04-25 15:18 ` dberlin at dberlin dot org
2005-04-26 12:36 ` dberlin at gcc dot gnu dot org
2005-04-28 2:35 ` belyshev at depni dot sinp dot msu dot ru
2005-04-28 23:38 ` cvs-commit at gcc dot gnu dot org
2005-05-10 17:32 ` pinskia at gcc dot gnu dot org
2005-05-10 22:31 ` pinskia at gcc dot gnu dot org
2005-05-11 10:51 ` pinskia at gcc dot gnu dot org
2005-05-17 11:35 ` pinskia at gcc dot gnu dot org
2005-05-18 6:05 ` pinskia at gcc dot gnu dot org
2005-05-22 18:47 ` pinskia at gcc dot gnu dot org
2005-06-12 13:24 ` pinskia at gcc dot gnu dot org
[not found] <bug-21173-7665@http.gcc.gnu.org/bugzilla/>
2006-03-22 20:54 ` pinskia at gcc dot gnu dot org
2006-03-28 17:40 ` pinskia 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=20050425140315.4828.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).