Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 989554 - regressions in gcc upstream suite on x86_64
Summary: regressions in gcc upstream suite on x86_64
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gcc
Version: 7.0
Hardware: x86_64
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: qe-baseos-tools
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-29 14:16 UTC by Dagmar Prokopová
Modified: 2015-03-31 18:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-03-31 18:46:57 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Dagmar Prokopová 2013-07-29 14:16:44 UTC
Description of problem:
While comparing the results of upstream-suite from gcc-4.8.1-2.el7 to results from gcc-4.4.7-3.el6 I found the following regressions:

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

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

In both cases the failure is probably caused by 'a' being optimized out.

Breakpoint 1 at 0x400699: file ./gcc.dg/guality/pr43051-1.c, line 39.
Breakpoint 1, bar (c=<optimized out>, v=1, e=0x601070 <a+16>)
    at ./gcc.dg/guality/pr43051-1.c:39
39	      foo ("c", (__UINTPTR_TYPE__) c, 3);	/* { dg-final { gdb-test 39 "c" "\&a\[0\]" } } */
$1 = <optimized out>
$2 = (struct S *) 0x601060 <a>
<optimized out> != (struct S *) 0x601060 <a>

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
run the upstream suite on rhel7 and rhel6 and compare the results

Actual results:
regressions mentioned above

Expected results:
no regressions

Additional info:

Comment 2 Marek Polacek 2013-08-02 11:10:53 UTC
Reproduced even with trunk.
This is caused by (one of the fixes for PR54693),

The $1 = <value optimized out> is caused by loop header copying, thus -fno-tree-ch makes it back into $1 = (struct S *) 0x600aa0.

Comment 3 Jakub Jelinek 2013-08-28 12:14:31 UTC
Very low priority.

Note You need to log in before you can comment on or make changes to this bug.