public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7147: ifcvt.c problem (regression)
Date: Thu, 18 Jul 2002 06:06:00 -0000	[thread overview]
Message-ID: <20020718130602.26799.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/7147; it has been noted by GNATS.

From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-gnats@gcc.gnu.org,gcc-patches@gcc.gnu.org,
 Mark Mitchell <mark@codesourcery.com>
Subject: Re: optimization/7147: ifcvt.c problem (regression)
Date: Thu, 18 Jul 2002 15:05:16 +0200

 At 23:27 16.07.2002, Richard Henderson wrote:
 >This looks like fallout from
 >
 >2002-05-03  Richard Henderson  <rth@redhat.com>
 >
 >         PR opt/6534
 >         * ifcvt.c (noce_try_store_flag, noce_try_store_flag_constants,
 >         noce_try_store_flag_inc, noce_try_store_flag_mask, noce_try_cmove,
 >         noce_try_cmove_arith, noce_try_minmax, noce_try_abs): Insert new
 >         code before JUMP, not EARLIEST.
 >
 >I'm testing the following on x86.  Give it a whirl on ppc as well?
 >
 >
 >r~
 >
 >
 >         * ifcvt.c (noce_get_condition): Make certain that the condition
 >         is valid at JUMP.
 
 That fixes the small executable testcase I posted and inspection of the 
 assembly shows that the original mozilla source code is fine too now. 
 Bootstrap and regression testing on powerpc-linux-gnu without problems.
 
 Franz.
 


             reply	other threads:[~2002-07-18 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  6:06 Franz Sirl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-29  9:42 sayle
2002-07-18  6:26 Mark Mitchell
2002-07-16 14:36 Richard Henderson
2002-06-30 19:06 Franz Sirl
2002-06-27 16:06 Franz.Sirl-kernel

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=20020718130602.26799.qmail@sources.redhat.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).