public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belyshev at depni dot sinp dot msu dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19579] [3.3/3.4/4.0 regression] -march=i686 generates a bogus program
Date: Sun, 23 Jan 2005 21:32:00 -0000	[thread overview]
Message-ID: <20050123213211.13301.qmail@sourceware.org> (raw)
In-Reply-To: <20050123002852.19579.abulmo@club-internet.fr>


------- Additional Comments From belyshev at depni dot sinp dot msu dot ru  2005-01-23 21:32 -------
I can confirm this bug on mainline with this testcase:
------------------------------------------------------------------------------
void abort (void);

int f ()
{
  return 0;
}

void __attribute__((noinline)) g (int k, int l)
{
  int j;
  
  if (f ())
    {
      j = k + l;
    }
  else
    {
      j = k + l + 1;
      if (j > 0)
	j++;
      else
	if (j < 0)
	  j--;
    }

  if (j % 2 != 0)
    abort ();
}

int main ()
{
  g (-2, 0);
  return 0;
}
------------------------------------------------------------------------------

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|3.3.4 3.3.5 3.4.0 3.4.3     |3.3.4 3.3.5 3.4.0 3.4.3
                   |                            |4.0.0
      Known to work|3.3.3 4.0.0                 |3.3.3
            Summary|[3.3/3.4 regression] -      |[3.3/3.4/4.0 regression] -
                   |march=i686 generates a bogus|march=i686 generates a bogus
                   |program                     |program


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


  parent reply	other threads:[~2005-01-23 21:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23  0:29 [Bug c/19579] New: " abulmo at club-internet dot fr
2005-01-23  0:31 ` [Bug target/19579] " pinskia at gcc dot gnu dot org
2005-01-23 21:15 ` [Bug target/19579] [3.3/3.4 regression] " reichelt at gcc dot gnu dot org
2005-01-23 21:32 ` belyshev at depni dot sinp dot msu dot ru [this message]
2005-01-23 22:06 ` [Bug target/19579] [3.3/3.4/4.0 " steven at gcc dot gnu dot org
2005-01-23 22:08 ` steven at gcc dot gnu dot org
2005-01-23 22:13 ` steven at gcc dot gnu dot org
2005-01-23 22:14 ` pinskia at gcc dot gnu dot org
2005-01-23 22:25 ` kazu at cs dot umass dot edu
2005-01-23 23:50 ` [Bug rtl-optimization/19579] [3.3/3.4/4.0 regression] -march=i686 generates a bogus program for x86* steven at gcc dot gnu dot org
2005-01-24  0:02 ` steven at gcc dot gnu dot org
2005-01-24  0:35 ` steven at gcc dot gnu dot org
2005-01-24  9:40 ` steven at gcc dot gnu dot org
2005-01-24 10:30 ` jakub at gcc dot gnu dot org
2005-01-24 11:31 ` jakub at gcc dot gnu dot org
2005-01-24 14:13 ` pinskia at gcc dot gnu dot org
2005-01-25 23:09 ` cvs-commit at gcc dot gnu dot org
2005-01-26  1:19 ` [Bug rtl-optimization/19579] [3.3/3.4 " pinskia at gcc dot gnu dot org
2005-02-10 20:35 ` cvs-commit at gcc dot gnu dot org
2005-02-10 20:42 ` [Bug rtl-optimization/19579] [3.3 " pinskia at gcc dot gnu dot org
2005-04-28  8:34 ` gdr at gcc dot gnu dot org
2005-05-01  7:23 ` cvs-commit at gcc dot gnu dot org
2005-05-01 13:17 ` 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=20050123213211.13301.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).