public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peter.ganzhorn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66625] New: xorg-server (Ext/Xinerama) fails to build with -O3 optimizations
Date: Mon, 22 Jun 2015 13:27:00 -0000 [thread overview]
Message-ID: <bug-66625-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66625
Bug ID: 66625
Summary: xorg-server (Ext/Xinerama) fails to build with -O3
optimizations
Product: gcc
Version: 5.1.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: peter.ganzhorn at gmail dot com
Target Milestone: ---
GCC 5.1.0 fails to build xorg-server with the -O3 option with the following
output:
xvdisp.c: In function ‘XineramifyXv’:
xvdisp.c:1783:37: error: array subscript is above array bounds
[-Werror=array-bounds]
if (MatchingAdaptors[k] && (MatchingAdaptors[k]->nPorts > j))
^
xvdisp.c:1784:31: error: array subscript is above array bounds
[-Werror=array-bounds]
port->info[k].id = MatchingAdaptors[k]->base_id + j;
^
xvdisp.c:1786:31: error: array subscript is above array bounds
[-Werror=array-bounds]
port->info[k].id = 0;
^
cc1: some warnings being treated as errors
Makefile:777: recipe for target 'xvdisp.lo' failed
This does *NOT* happen with gcc-4.9.
The xorg guys think this has to be a gcc bug.
Here is the bug report on their bug tracker:
Bug #91031 https://bugs.freedesktop.org/show_bug.cgi?id=91031
See their bug report for a more detailed explaination why they blame gcc and
not their code.
I'm running/building with
- Distro: Arch Linux (rolling-release, up-to-date)
- gcc-5.1 is from the official Arch Linux repo.
- Intel x64_64 (Haswell) with -march=native and -mtune=native
I have the following build options set via /etc/makepkg.conf (which is used for
package compilation from source on Arch Linux):
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=native -mtune=native -O3 -pipe -fstack-protector-strong
--param=ssp-buffer-size=4"
CXXFLAGS="-march=native -mtune=native -O3 -pipe -fstack-protector-strong
--param=ssp-buffer-size=4"
LDFLAGS="-Wl,-O2,--sort-common,--as-needed,-z,relro"
MAKEFLAGS="-j16"
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
Changing -O3 to -O2 makes the build complete without fatal errors and results
in a working xorg-server.
>From gcc-bugs-return-489591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jun 22 13:29:36 2015
Return-Path: <gcc-bugs-return-489591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91569 invoked by alias); 22 Jun 2015 13:29:36 -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 91525 invoked by uid 48); 22 Jun 2015 13:29:33 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65914] [6 Regression] error: unrecognizable insn
Date: Mon, 22 Jun 2015 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-65914-4-fVkLg9lc1Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65914-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65914-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-06/txt/msg01923.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide914
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot gnu.org
--- Comment #9 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Will let this burn in for a week, and then plan to backport to 4.9/5.
next reply other threads:[~2015-06-22 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 13:27 peter.ganzhorn at gmail dot com [this message]
2015-06-22 14:10 ` [Bug c/66625] " rguenth at gcc dot gnu.org
2015-10-20 9:29 ` [Bug tree-optimization/66625] " mpolacek 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-66625-4@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).