public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhowells at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/61812] gcc ICE incorrectly says "The bug is not reproducible, so it is likely a hardware or OS problem."
Date: Tue, 15 Jul 2014 17:42:00 -0000 [thread overview]
Message-ID: <bug-61812-4-hN4l9wQIan@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61812-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61812
--- Comment #5 from dhowells at redhat dot com <dhowells at redhat dot com> ---
(In reply to Andrew Pinski from comment #4)
> Also even though it might be a true gcc issue, it does not say it is a
> hardware issue, the message says likely. This could also mean a gc or a
> memory issue inside gcc. Except detecting that vs a memory issue is much
> harder.
It's a bug with the code on the redhat/ branch that generates this message.
The problem is that when it detects an ICE, the gcc driver runs the cc1 binary
twice more and compares the output - but the output contains a userspace
pointer from within gcc itself, eg:
(call (mem:QI (symbol_ref:SI ("abort") [flags 0x41] <function_decl
0x7f5784e05d00 abort>) [0 __builtin_abort S1 A8])
and this may legitimately differ due to the kernel mapping things in different
places during execve() and mmap().
next prev parent reply other threads:[~2014-07-15 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 14:54 [Bug c/61812] New: gcc ICE " dhowells at redhat dot com
2014-07-15 14:57 ` [Bug c/61812] gcc ICE incorrectly " dhowells at redhat dot com
2014-07-15 15:51 ` schwab@linux-m68k.org
2014-07-15 16:37 ` dhowells at redhat dot com
2014-07-15 16:44 ` pinskia at gcc dot gnu.org
2014-07-15 17:42 ` dhowells at redhat dot com [this message]
2014-07-15 18:02 ` jakub at gcc dot gnu.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-61812-4-hN4l9wQIan@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).