public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/20623] ICE: fold check: original tree changed by fold with --enable-checking=fold Date: Sat, 26 Jan 2008 07:18:00 -0000 [thread overview] Message-ID: <20080126051138.20225.qmail@sourceware.org> (raw) In-Reply-To: <bug-20623-7559@http.gcc.gnu.org/bugzilla/> ------- Comment #38 from ghazi at gcc dot gnu dot org 2008-01-26 05:11 ------- Update: mainline appears to pass fold checking albeit with a few extra timeouts due to length compilation times. However the last fix for fold checking was never backported to the branches. On 4.1/4.2 I still get these extra fold checking errors due to label addresses: FAIL: gcc.c-torture/compile/20021108-1.c FAIL: gcc.c-torture/compile/920501-7.c FAIL: gcc.c-torture/compile/labels-1.c FAIL: gcc.c-torture/compile/labels-2.c FAIL: gcc.c-torture/compile/labels-3.c FAIL: gcc.dg/20021029-1.c FAIL: gcc.dg/pr16973.c Here are the latest results for x86_64-unknown-linux-gnu: 4.1 (extra errors): http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg01221.html 4.2 (extra errors): http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg01222.html trunk (x86_64 ok): http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg01253.html I don't have access to solaris any more to see if there are still gomp fold checking failures as from comment #37. -- ghazi at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|4.0.4 4.1.2 |4.0.4 4.1.2 4.1.3 4.2.2 | |4.2.3 Known to work| |4.3.0 Last reconfirmed|2007-06-30 02:16:08 |2008-01-26 05:11:37 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20623
next prev parent reply other threads:[~2008-01-26 5:12 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20623-7559@http.gcc.gnu.org/bugzilla/> 2005-10-25 19:20 ` pinskia at gcc dot gnu dot org 2005-10-26 14:17 ` micis at gmx dot de 2005-10-26 16:55 ` pinskia at gcc dot gnu dot org 2006-02-16 2:51 ` ghazi at gcc dot gnu dot org 2006-02-21 13:59 ` ghazi at gcc dot gnu dot org 2006-06-02 20:12 ` rsa at us dot ibm dot com 2007-01-16 4:52 ` ghazi at gcc dot gnu dot org 2007-01-18 14:42 ` ghazi at gcc dot gnu dot org 2007-06-20 12:28 ` rguenth at gcc dot gnu dot org 2007-06-20 18:50 ` spop at gcc dot gnu dot org 2007-06-20 22:46 ` rob1weld at aol dot com 2007-06-20 22:58 ` spop at gcc dot gnu dot org 2007-06-20 23:32 ` spop at gcc dot gnu dot org 2007-06-21 8:00 ` rguenther at suse dot de 2007-06-21 8:02 ` rguenther at suse dot de 2007-06-21 8:16 ` richard dot guenther at gmail dot com 2007-06-21 8:21 ` spop at gcc dot gnu dot org 2007-06-21 8:48 ` rguenther at suse dot de 2007-06-21 10:07 ` richard dot guenther at gmail dot com 2007-06-21 18:21 ` spop at gcc dot gnu dot org 2007-06-21 19:33 ` rguenther at suse dot de 2007-06-21 20:56 ` spop at gcc dot gnu dot org 2007-06-21 21:25 ` spop at gcc dot gnu dot org 2007-06-24 2:23 ` rob1weld at aol dot com 2007-06-24 17:46 ` rob1weld at aol dot com 2007-06-24 18:41 ` ghazi at gcc dot gnu dot org 2007-06-25 5:06 ` rob1weld at aol dot com 2007-06-25 5:44 ` ghazi at gcc dot gnu dot org 2007-06-30 2:16 ` ghazi at gcc dot gnu dot org 2007-06-30 2:23 ` ghazi at gcc dot gnu dot org 2008-01-26 7:18 ` ghazi at gcc dot gnu dot org [this message] 2009-08-12 14:22 ` rmansfield at qnx dot com 2010-02-27 14:06 ` zsojka at seznam dot cz [not found] <bug-20623-4@http.gcc.gnu.org/bugzilla/> 2021-08-17 2:46 ` pinskia at gcc dot gnu.org 2005-03-24 15:07 [Bug tree-optimization/20623] New: " micis at gmx dot de 2005-04-16 16:38 ` [Bug middle-end/20623] " pinskia at gcc dot gnu dot org 2005-05-31 16:57 ` pinskia at gcc dot gnu dot org 2005-07-04 21:16 ` pinskia at gcc dot gnu dot org 2005-07-05 10:49 ` micis at gmx dot de 2005-08-18 5:02 ` pinskia at gcc dot gnu dot org 2005-08-18 6:39 ` pinskia at gcc dot gnu dot org 2005-08-29 0:12 ` dberlin 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=20080126051138.20225.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: linkBe 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).