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 middle-end/19454] [4.0 Regression] bad code generated with gcc.c-torture/execute/bf64-1.c at -O1 Date: Fri, 01 Apr 2005 11:23:00 -0000 [thread overview] Message-ID: <20050401112326.25440.qmail@sourceware.org> (raw) In-Reply-To: <20050115005010.19454.sje@cup.hp.com> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-01 11:23 ------- Subject: Bug 19454 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-4_0-branch Changes by: bonzini@gcc.gnu.org 2005-04-01 11:23:08 Modified files: gcc : ChangeLog combine.c gcc/config/i386: i386.c Log message: 2005-04-01 Paolo Bonzini <bonzini@gnu.org> PR middle-end/19454 PR rtl-optimization/20600 * combine.c (gen_binary): Remove. (known_cond, simplify_shift_const, find_split_point, combine_simplify_rtx, simplify_if_then_else, simplify_set, simplify_logical, expand_field_assignment, extract_left_shift, force_to_mode, if_then_else_cond, apply_distributive_law, simplify_and_const_int, simplify_shift_const, gen_lowpart_for_combine, simplify_comparison, reversed_comparison): Replace with simplify_gen_binary, simplify_gen_relational or distribute_and_simplify_rtx. (distribute_and_simplify_rtx): New function. * config/i386/i386.c (ix86_decompose_address): Look inside SUBREGs to fix addresses involving EBP and ESP. (aligned_operand, legitimate_address_p, ix86_address_cost): Be prepared for SUBREGed registers. (legitimate_address_p): Accept SUBREGed registers. 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.107&r2=2.7592.2.108 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/combine.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.475.4.1&r2=1.475.4.2 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/i386/i386.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.795.6.1&r2=1.795.6.2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19454
next prev parent reply other threads:[~2005-04-01 11:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-15 0:50 [Bug middle-end/19454] New: " sje at cup dot hp dot com 2005-01-15 1:42 ` [Bug middle-end/19454] [4.0 Regression] " pinskia at gcc dot gnu dot org 2005-02-01 18:44 ` pinskia at gcc dot gnu dot org 2005-03-05 19:57 ` [Bug middle-end/19454] [4.0/4.1 " pinskia at gcc dot gnu dot org 2005-03-20 2:53 ` [Bug middle-end/19454] [4.0 " jsm28 at gcc dot gnu dot org 2005-03-21 14:24 ` bonzini at gcc dot gnu dot org 2005-03-24 17:44 ` bonzini at gcc dot gnu dot org 2005-04-01 8:25 ` bonzini at gcc dot gnu dot org 2005-04-01 11:23 ` cvs-commit at gcc dot gnu dot org [this message] 2005-04-04 10:29 ` jsm28 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=20050401112326.25440.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: linkBe 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).