public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sirl@gcc.gnu.org
To: sirl@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: bootstrap/9994
Date: Tue, 11 Mar 2003 19:26:00 -0000 [thread overview]
Message-ID: <20030311192601.3127.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/9994; it has been noted by GNATS.
From: sirl@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: bootstrap/9994
Date: 11 Mar 2003 19:25:24 -0000
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-3_3-branch
Changes by: sirl@gcc.gnu.org 2003-03-11 19:25:24
Modified files:
gcc : recog.c sbitmap.c sbitmap.h ChangeLog
Log message:
2003-03-11 Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
PR bootstrap/9994
Backport from mainline:
2003-02-18 Roger Sayle <roger@eyesopen.com>
* sbitmap.c (sbitmap_resize): New function.
* sbitmap.h (sbitmap_resize): Prototype here.
* recog.c (split_all_insns): Use sbitmap_resize.
Mon Feb 17 16:16:54 CET 2003 Jan Hubicka <jh@suse.cz>
* recog.c (split_all_insns): Fix memory overflow.
2003-02-15 Richard Henderson <rth@redhat.com>
* recog.c (split_all_insns): Include new blocks in life update;
do a global life update.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/recog.c.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.168.2.1&r2=1.168.2.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/sbitmap.c.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.23&r2=1.23.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/sbitmap.h.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.18&r2=1.18.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.16114.2.283&r2=1.16114.2.284
reply other threads:[~2003-03-11 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030311192601.3127.qmail@sources.redhat.com \
--to=sirl@gcc.gnu.org \
--cc=gcc-prs@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).