public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at oberhumer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/25196]  New: i386: wrong arguments passed
Date: Thu, 01 Dec 2005 06:05:00 -0000	[thread overview]
Message-ID: <bug-25196-4672@http.gcc.gnu.org/bugzilla/> (raw)

I really had a hard time tracking this down from a large program: gcc 4.0.2 on
i386-linux sometimes passes wrong arguments.

Please try the attached source file on i386 with "gcc-4.0.2 -march=i386 -O3
-fomit-frame-pointer".

When looking at the disassembly of f2() it seems that %edi is incorrectly used
twice:

  5e:   89 f8                   mov    %edi,%eax   !!!!!
  60:   ff 74 24 24             pushl  0x24(%esp)
  64:   55                      push   %ebp
  65:   89 f9                   mov    %edi,%ecx   !!!!!
  67:   89 da                   mov    %ebx,%edx
  69:   e8 92 ff ff ff          call   0 <f1>

This wrong-code bug is probably a 3.2, 3.3 and 3.4 regression.

~Markus


-- 
           Summary: i386: wrong arguments passed
           Product: gcc
           Version: 4.0.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: markus at oberhumer dot com
  GCC host triplet: i386-pc-linux


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


             reply	other threads:[~2005-12-01  6:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01  6:05 markus at oberhumer dot com [this message]
2005-12-01  6:06 ` [Bug target/25196] " markus at oberhumer dot com
2005-12-01  7:02 ` [Bug target/25196] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-12-19 18:50 ` mmitchel at gcc dot gnu dot org
2005-12-20  9:17 ` [Bug rtl-optimization/25196] " belyshev at depni dot sinp dot msu dot ru
2005-12-20 10:17 ` steven at gcc dot gnu dot org
2005-12-20 10:18 ` steven at gcc dot gnu dot org
2005-12-20 10:59 ` belyshev at depni dot sinp dot msu dot ru
2005-12-20 14:59 ` steven at gcc dot gnu dot org
2005-12-20 15:58 ` steven at gcc dot gnu dot org
2005-12-21 15:46 ` [Bug rtl-optimization/25196] [4.0 " steven at gcc dot gnu dot org
2006-01-27 18:03 ` markus at oberhumer dot com
2006-02-27 20:21 ` mmitchel at gcc dot gnu dot org
2006-02-27 21:13 ` steven at gcc dot gnu dot org
2006-02-27 21:34 ` steven 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=bug-25196-4672@http.gcc.gnu.org/bugzilla/ \
    --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).