No subject


Thu Feb 5 07:19:00 GMT 2015


https://gcc.gnu.org/ml/gcc-testresults/2015-02/msg00497.html


FAIL: gcc.dg/guality/pr43051-1.c   -O1  line 34 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions  line 34 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O3 -fomit-frame-pointer -funroll-loops 
line 34 c == &a[0]


FAIL: gcc.dg/guality/pr43077-1.c   -O1  line 42 varb == 2
FAIL: gcc.dg/guality/pr43077-1.c   -O2  line 42 varc == 3
FAIL: gcc.dg/guality/pr43077-1.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  line 42 varc == 3
FAIL: gcc.dg/guality/pr43077-1.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  line 42 varc == 3
FAIL: gcc.dg/guality/pr43077-1.c   -O3 -fomit-frame-pointer  line 42 varc == 3
FAIL: gcc.dg/guality/pr43077-1.c   -O3 -g  line 42 varc == 3
FAIL: gcc.dg/guality/pr43077-1.c   -Os  line 42 varc == 3

From
https://gcc.gnu.org/ml/gcc-testresults/2015-02/msg00117.html

On AArch64 things look even worse but I suspect that some of these failures are
more to do with which version of gdb was used.  

FAIL: gcc.dg/guality/pr43051-1.c   -O1  line 34 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O2  line 34 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O2  line 39 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O2  line 40 v == 1
FAIL: gcc.dg/guality/pr43051-1.c   -O2  line 41 e == &a[1]
FAIL: gcc.dg/guality/pr43051-1.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  line 34 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  line 39 c == &a[0]
FAIL: gcc.dg/guality/pr43051-1.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  line 40 v == 1
FAIL: gccReceived: (qmail 17839 invoked by uid 48); 5 Feb 2015 07:19:14 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/64942] New: FAIL: pr43077-1.c and pr43051-1.c
Date: Thu, 05 Feb 2015 07:19:12 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-64942-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

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

            Bug ID: 64942
           Summary: FAIL: pr43077-1.c and pr43051-1.c
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ramana at gcc dot gnu.org

These appear to be real debug info issues rather than testisms and they fail on
arm / aarch64.



More information about the Gcc-bugs mailing list