public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28403] [4.0/4.1 Regression] Missed argument pop after doubleword shift
Date: Wed, 26 Jul 2006 13:35:00 -0000	[thread overview]
Message-ID: <20060726133543.22098.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28403-4496@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from rsandifo at gcc dot gnu dot org  2006-07-26 13:35 -------
Subject: Bug 28403

Author: rsandifo
Date: Wed Jul 26 13:35:34 2006
New Revision: 115758

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115758
Log:
gcc/
        PR middle-end/28403
        * optabs.c (expand_doubleword_shift): Wrap the call to
        do_compare_rtx_and_jump with NO_DEFER_POP and OK_DEFER_POP.

gcc/testsuite/
        PR middle-end/28403
        * gcc.c-torture/execute/pr28403.c: New test.

Added:
    branches/gcc-4_0-branch/gcc/testsuite/gcc.c-torture/execute/pr28403.c
Modified:
    branches/gcc-4_0-branch/gcc/ChangeLog
    branches/gcc-4_0-branch/gcc/optabs.c
    branches/gcc-4_0-branch/gcc/testsuite/ChangeLog


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28403


  parent reply	other threads:[~2006-07-26 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  8:20 [Bug middle-end/28403] New: [4.0/4.1/4.2 " rsandifo at gcc dot gnu dot org
2006-07-17  8:21 ` [Bug middle-end/28403] " rsandifo at gcc dot gnu dot org
2006-07-17 15:31 ` rsandifo at gcc dot gnu dot org
2006-07-17 15:34 ` rsandifo at gcc dot gnu dot org
2006-07-20  8:32 ` rsandifo at gcc dot gnu dot org
2006-07-22 14:25 ` [Bug middle-end/28403] [4.0/4.1 " pinskia at gcc dot gnu dot org
2006-07-22 14:25 ` pinskia at gcc dot gnu dot org
2006-07-26 13:32 ` rsandifo at gcc dot gnu dot org
2006-07-26 13:35 ` rsandifo at gcc dot gnu dot org [this message]
2006-07-26 13:39 ` rsandifo 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=20060726133543.22098.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).