public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goeland86 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52811] New: -O3 flag makes xorg-server-1.11.4 compile fail on amd64
Date: Sat, 31 Mar 2012 20:50:00 -0000	[thread overview]
Message-ID: <bug-52811-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52811

             Bug #: 52811
           Summary: -O3 flag makes xorg-server-1.11.4 compile fail on
                    amd64
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: goeland86@gmail.com


When compiling xorg-server-1.11.4 with the -O3 optimization flag enabled, the
compilation of xorg-server fails in xf86EdidModes.c at line 747, about an array
subscript being above array bounds.

Recompiling with the -O2 flag the error disappears without any other changes to
the configuration.

I ran into the problem with gcc-4.5.3 today, but I ran into it several months
back, possibly with 4.5.2 (I'm not quite sure, and didn't think it was gcc
related at the time.)

This happened on Gentoo reportedly to others besides myself, according to
echoes in #gentoo on irc.freenode.net.


             reply	other threads:[~2012-03-31 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 20:50 goeland86 at gmail dot com [this message]
2012-03-31 21:01 ` [Bug target/52811] " redi at gcc dot gnu.org
2012-03-31 22:42 ` goeland86 at gmail dot com

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