public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/56023] [4.6 Regression]: [alpha] -fcompare-debug failure due to sched1 pass
Date: Thu, 17 Jan 2013 22:09:00 -0000	[thread overview]
Message-ID: <bug-56023-4-XCT9ycR2fL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56023-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-17 22:08:50 UTC ---
Created attachment 29197
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29197
Preprocessed source of the file that miscompares during bootstrap

This is the preprocessed source of the file that miscompares during bootstrap.

~/gcc-build-alpha/gcc/xgcc -B ~/gcc-build-alpha/gcc -O2 -fcompare-debug -S
opts.i
xgcc: error: opts.i: -fcompare-debug failure


  reply	other threads:[~2013-01-17 22:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 22:03 [Bug rtl-optimization/56023] New: " ubizjak at gmail dot com
2013-01-17 22:09 ` ubizjak at gmail dot com [this message]
2013-01-17 22:11 ` [Bug rtl-optimization/56023] " ubizjak at gmail dot com
2013-01-17 23:00 ` ubizjak at gmail dot com
2013-01-18 10:19 ` rguenth at gcc dot gnu.org
2013-01-18 17:05 ` ubizjak at gmail dot com
2013-01-18 17:38 ` ubizjak at gmail dot com
2013-01-18 17:49 ` ubizjak at gmail dot com
2013-01-19 10:06 ` ubizjak at gmail dot com
2013-01-19 10:18 ` ubizjak at gmail dot com
2013-01-19 19:46 ` ubizjak at gmail dot com
2013-01-19 21:07 ` ubizjak at gmail dot com
2013-01-21 17:52 ` uros at gcc dot gnu.org
2013-01-21 18:00 ` uros at gcc dot gnu.org
2013-01-21 18:04 ` uros at gcc dot gnu.org
2013-01-21 18:10 ` ubizjak at gmail dot com

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-56023-4-XCT9ycR2fL@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).