public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/21138] wrong code in sixtrack for -fmodulo-sched
Date: Thu, 28 Apr 2005 00:07:00 -0000	[thread overview]
Message-ID: <20050428000714.12078.qmail@sourceware.org> (raw)
In-Reply-To: <20050421005103.21138.janis@gcc.gnu.org>


------- Additional Comments From janis at gcc dot gnu dot org  2005-04-28 00:07 -------
There are other SPEC CPU2000 comparison failures on powerpc64-linux
with "-m64 -O2 -fmodulo-sched" that resist attempts to minimize the
testcases.  apsi has been failing since:
                                                                                
  http://gcc.gnu.org/ml/gcc-cvs/2005-04/msg00893.html from kazu
                                                                                
and lucas has been failing since:
                                                                                
  http://gcc.gnu.org/ml/gcc-cvs/2005-04/msg01289.html from radkver.
                                                                                
While trying to minimize the apsi failure I added write statements
that caused apsi to segfault; for example, write the value of I just
inside the loop using it in DCDTZ with:
                                                                                
1327a1328,1329
>             write(6,1001) i
> 1001        format(' i = ',i3)
                                                                                
I'm adding the information to this PR because I don't have test cases
to submit for the apsi and lucas failures in new PRs, and hope that
the information might be useful to Mostafa or anyone else who looks
into this PR.  There were other failures with these options earlier
this month that have since gone away, making it look even more like
latent bugs in the modulo scheduling code.
                                                                                
All of these SPEC CPU2000 failures are with the small "test" input.

-- 


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


  parent reply	other threads:[~2005-04-28  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21  0:51 [Bug tree-optimization/21138] New: " janis at gcc dot gnu dot org
2005-04-21  0:51 ` [Bug tree-optimization/21138] " janis at gcc dot gnu dot org
2005-04-21  0:54 ` [Bug rtl-optimization/21138] " pinskia at gcc dot gnu dot org
2005-04-22  0:26 ` janis at gcc dot gnu dot org
2005-04-22 13:56 ` rakdver at gcc dot gnu dot org
2005-04-28  0:07 ` janis at gcc dot gnu dot org [this message]
2005-05-04 12:31 ` mustafa at il dot ibm dot com
2005-05-09 19:32 ` janis at gcc dot gnu dot org
2005-05-16 20:27 ` janis at gcc dot gnu dot org
2005-05-17 15:07 ` mustafa at il dot ibm dot com
2005-05-17 20:01 ` janis187 at us dot ibm dot com
2005-06-01  5:27 ` cvs-commit at gcc dot gnu dot org
2005-06-01 19: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=20050428000714.12078.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).