public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Stephane.Carrez@worldnet.fr
To: gcc-gnats@gcc.gnu.org
Subject: optimization/5854: initialize_uninitialized_subregs() breaks HC11/HC12 port
Date: Wed, 06 Mar 2002 12:36:00 -0000 [thread overview]
Message-ID: <20020306202815.27371.qmail@sources.redhat.com> (raw)
>Number: 5854
>Category: optimization
>Synopsis: initialize_uninitialized_subregs() breaks HC11/HC12 port
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 06 12:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Stephane Carrez
>Release: 3_1-20020305
>Organization:
>Environment:
>Description:
The patch:
http://gcc.gnu.org/ml/gcc-patches/2001-11/msg01067.html
From: Andrew Macleod <amacleod at cygnus dot com>
* rtl.h (initialize_uninitialized_subregs): New prototype.
* toplev.c (rest_of_compilation): Call initialize_uninitialized_subregs
when optimization is on.
* flow.c (find_regno_partial): Find subregs within an expression.
(initialize_uninitialized_subregs): Initialize live on entry registers
which are used in subreg expressions.
creates a regression on m6811 target compared to 3.0.3/3.0.4
It is no longer possible to build the libgcc2 library.
Removing or disabling the call to
initialize_uninitialized_subregs() solves the problem.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-03-06 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 12:36 Stephane.Carrez [this message]
2002-03-20 2:02 jakub
2002-03-20 13:56 ciceron
2002-03-21 15:42 jakub
2002-04-04 2:17 jakub
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=20020306202815.27371.qmail@sources.redhat.com \
--to=stephane.carrez@worldnet.fr \
--cc=gcc-gnats@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).