public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/67002] [5] [SH]: Bootstrap stage 2/3 comparison failure - gcc/real.o differs
Date: Thu, 06 Aug 2015 02:04:00 -0000	[thread overview]
Message-ID: <bug-67002-4-pmD2m7GJGX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67002-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67002

--- Comment #18 from Kazumoto Kojima <kkojima at gcc dot gnu.org> ---
(In reply to Michael Karcher from comment #15)
The first different line of diff of the .pre dumps of Michael's
test case with/without -g is:

< Expression hash table (53 buckets, 12 entries)
---
> Expression hash table (51 buckets, 12 entries)

It means that gcse.c:alloc_hash_table allocates the table with
different number of buckets with -g.
It looks emit_rtl.c:get_max_insn_count returns different values
with/without -g at rtl_pre pass.  This shouldn't happen.
The comment of get_max_insn_count says:

  /* The table size must be stable across -g, to avoid codegen
     differences due to debug insns, and not be affected by
     -fmin-insn-uid, to avoid excessive table size and to simplify
     debugging of -fcompare-debug failures.  */


  parent reply	other threads:[~2015-08-06  2:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 19:39 [Bug target/67002] New: " glaubitz at physik dot fu-berlin.de
2015-07-25  6:12 ` [Bug target/67002] " olegendo at gcc dot gnu.org
2015-07-26 16:42 ` glaubitz at physik dot fu-berlin.de
2015-07-29  7:11 ` glaubitz at physik dot fu-berlin.de
2015-07-29  7:13 ` glaubitz at physik dot fu-berlin.de
2015-07-29  7:18 ` glaubitz at physik dot fu-berlin.de
2015-07-29  8:03 ` kkojima at gcc dot gnu.org
2015-07-29 12:29 ` glaubitz at physik dot fu-berlin.de
2015-07-29 12:37 ` olegendo at gcc dot gnu.org
2015-07-30 12:35 ` olegendo at gcc dot gnu.org
2015-08-03  9:07 ` glaubitz at physik dot fu-berlin.de
2015-08-04  0:06 ` kkojima at gcc dot gnu.org
2015-08-05 22:46 ` gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
2015-08-06  1:18 ` olegendo at gcc dot gnu.org
2015-08-06  2:04 ` kkojima at gcc dot gnu.org [this message]
2015-08-06 11:57 ` kkojima at gcc dot gnu.org
2015-08-06 23:24 ` kkojima at gcc dot gnu.org
2015-08-07  0:16 ` olegendo at gcc dot gnu.org
2015-08-07 20:42 ` kkojima at gcc dot gnu.org
2015-08-07 20:48 ` kkojima at gcc dot gnu.org
2015-08-13  6:28 ` glaubitz at physik dot fu-berlin.de
2015-08-13 13:17 ` olegendo at gcc dot gnu.org
2015-08-14  8:26 ` glaubitz at physik dot fu-berlin.de
2015-08-14  9:31 ` glaubitz at physik dot fu-berlin.de

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-67002-4-pmD2m7GJGX@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).