public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/66314] New: ice in verify_loop_structure
@ 2015-05-27 19:15 dcb314 at hotmail dot com
  2015-05-28  7:34 ` [Bug middle-end/66314] " rguenth at gcc dot gnu.org
                   ` (12 more replies)
  0 siblings, 13 replies; 14+ messages in thread
From: dcb314 at hotmail dot com @ 2015-05-27 19:15 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 66314
           Summary: ice in verify_loop_structure
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 35637
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35637&action=edit
C source code

For trunk gcc dated 20150527

crypto/asymmetric_keys/pkcs7_trust.c: In function ‘pkcs7_validate_trust’:
crypto/asymmetric_keys/pkcs7_trust.c:168:5: error: size of loop 2 should be 36,
not 38
 int pkcs7_validate_trust(struct pkcs7_message *pkcs7,
     ^
crypto/asymmetric_keys/pkcs7_trust.c:168:5: internal compiler error: in
verify_loop_structure, at cfgloop.c:1662
0x7166e3 verify_loop_structure()
        ../../src/trunk/gcc/cfgloop.c:1662
0xa13f47 loop_optimizer_init(unsigned int)
        ../../src/trunk/gcc/loop-init.c:124
0xe4a53a execute_vrp
        ../../src/trunk/gcc/tree-vrp.c:10377
0xe4a53a execute
        ../../src/trunk/gcc/tree-vrp.c:10474
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Flags -std=gnu89 -Os -fprofile-arcs -fsanitize=kernel-address
required. Code derived from Linux kernel, so probably quite important.
>From gcc-bugs-return-487432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 27 19:16:28 2015
Return-Path: <gcc-bugs-return-487432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26065 invoked by alias); 27 May 2015 19:16:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26030 invoked by uid 55); 27 May 2015 19:16:23 -0000
From: "andi at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/66305] -ffat-lto-objects create unreproducible objects
Date: Wed, 27 May 2015 19:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.1.1
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andi at firstfloor dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66305-4-XUQcYqWdja@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66305-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66305-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-05/txt/msg02272.txt.bz2
Content-length: 1201

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf305

--- Comment #4 from andi at firstfloor dot org ---
> --- Comment #3 from lunar at debian dot org ---
> Richard Biener:
> > I think they become deterministic with -frandom-seed=0 for example.
> > They are not deterministic to support partial linking of LTO objects as far
> > as I know.
>
> They are indeed reproducible with `-frandom-seed=0`. But I guess there's a
> downside to that, right?

The downside is that incremential linking (ld -r) does not work.
But the random seed is used for other things in gcc too, so you may
have other problems too.

> > similar, which would be a bit more deterministic, but there are still
> > ways this could break (e.g. if someone copies object files around)
>
> Would using a hash over the section content work? In any cases, in the context
> of Debian (this applies for FreeBSD as well), we have a canonical build path
> so it would probably be fine to use it as the source of the hash.
>
> I guess one could already do this without further help by giving the
> build path to `-frandom-seed=`. This only would need some Makefile trickery.

Yes. It would probably be easier in gcc, e.g. with a new option.


^ permalink raw reply	[flat|nested] 14+ messages in thread
end of thread, other threads:[~2015-08-03 16:27 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-27 19:15 [Bug c/66314] New: ice in verify_loop_structure dcb314 at hotmail dot com
2015-05-28  7:34 ` [Bug middle-end/66314] " rguenth at gcc dot gnu.org
2015-05-28  7:56 ` [Bug middle-end/66314] [6 Regression] " rguenth at gcc dot gnu.org
2015-05-28 14:44 ` rguenth at gcc dot gnu.org
2015-05-28 14:50 ` ktkachov at gcc dot gnu.org
2015-05-28 15:24 ` jakub at gcc dot gnu.org
2015-05-28 15:25 ` jakub at gcc dot gnu.org
2015-05-29 10:51 ` rguenth at gcc dot gnu.org
2015-05-29 11:07 ` rguenth at gcc dot gnu.org
2015-06-01 13:55 ` rguenth at gcc dot gnu.org
2015-06-01 13:58 ` rguenth at gcc dot gnu.org
2015-06-01 14:00 ` rguenth at gcc dot gnu.org
2015-07-21  8:11 ` trippels at gcc dot gnu.org
2015-08-03 16:27 ` law at redhat dot com

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).