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 fortran/18109] ICE with explicit array of strings
Date: Thu, 17 Feb 2005 13:15:00 -0000 [thread overview]
Message-ID: <20050217015628.13769.qmail@sourceware.org> (raw)
In-Reply-To: <20041022133113.18109.martin@mpa-garching.mpg.de>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-17 01:56 -------
Subject: Bug 18109
CVSROOT: /cvs/gcc
Module name: gcc
Branch: apple-ppc-branch
Changes by: dalej@gcc.gnu.org 2005-02-17 01:56:12
Modified files:
gcc : ChangeLog.apple-ppc cse.c simplify-rtx.c
recog.c basic-block.h
gcc/config/i386: i386.md
Log message:
2005-02-16 Dale Johannesen <dalej@apple.com>
Radar 4006687
PR 17767 et al (fix from mainline)
* cse.c (fold_rtx) [RTX_COMPARE, RTX_COMM_COMPARE]: Don't attempt
any simplifications of vector mode comparison operators.
* simplify-rtx.c (simplify_relational_operation): Fix variable name.
2005-02-15 Dale Johannesen <dalej@apple.com>
Radar 3991611
Radar 3990578
PRs 19084 and 19348 (fix from mainline)
* recog.c (peephole2_optimize): Do global life update if some peephole
decides it doesn't need at least one of its inputs and that change
influences liveness at the start of the basic block.
* basic-block.h (EXECUTE_IF_AND_COMPL_IN_REG_SET): Needs 2 REGSET
arguments instead of 1.
2005-02-15 Dale Johannesen <dalej@apple.com>
Radar 3876378
Radar 3838108
PR 18109 (fix from mainline)
* config/i386/i386.md (movhi_1): Remove previous attempt at a fix.
(movqi_1): Ditto. Don't use 4-byte load when unsafe.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.apple-ppc.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.1.2.308&r2=1.1.2.309
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cse.c.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.229.2.32.2.13&r2=1.229.2.32.2.14
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/simplify-rtx.c.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.107.2.31.2.11&r2=1.107.2.31.2.12
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/recog.c.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.159.2.24.2.8&r2=1.159.2.24.2.9
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/basic-block.h.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.153.2.48.2.10&r2=1.153.2.48.2.11
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/i386/i386.md.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.374.2.42.2.7&r2=1.374.2.42.2.8
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18109
next prev parent reply other threads:[~2005-02-17 1:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 13:31 [Bug fortran/18109] New: [gfortran] " martin at mpa-garching dot mpg dot de
2004-10-22 13:32 ` [Bug fortran/18109] " martin at mpa-garching dot mpg dot de
2004-10-22 13:42 ` [Bug fortran/18109] " pinskia at gcc dot gnu dot org
2004-10-22 13:45 ` martin at mpa-garching dot mpg dot de
2005-02-15 6:15 ` cvs-commit at gcc dot gnu dot org
2005-02-17 13:05 ` dalej at apple dot com
2005-02-17 13:15 ` cvs-commit at gcc dot gnu dot org [this message]
2005-05-31 17:20 ` cvs-commit at gcc dot gnu dot org
2005-06-05 9:02 ` cvs-commit at gcc dot gnu dot org
2005-06-05 22:39 ` pault at gcc dot gnu dot org
2005-06-05 22:42 ` 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=20050217015628.13769.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).