public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gbeauchesne at mandrakesoft dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/11559] New: [hammer-3.3 regression] Infinite loop while compiling kernel with VRP
Date: Thu, 17 Jul 2003 13:11:00 -0000	[thread overview]
Message-ID: <20030717131115.11559.gbeauchesne@mandrakesoft.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: [hammer-3.3 regression] Infinite loop while compiling
                    kernel with VRP
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gbeauchesne at mandrakesoft dot com
                CC: aj at suse dot de,gcc-bugs at gcc dot gnu dot org,jh at
                    suse dot cz
  GCC host triplet: i686-pc-linux-gnu

Hi, the testcase that is about to be attached fails to complete compilation
(after 1 day :) with the following flags: -mpreferred-stack-boundary=2 -Os
-fno-strict-aliasing -fno-common -fomit-frame-pointer -falign-functions=4. VRP
seems to be the culprit as compiling with only -O -fvrp also fails.

This bug is only available on GNU C version 3.3.1-hammer 20030703. This is a
regression since 3.3-hammer 2003/05/13 which didn't have VRP actually.


             reply	other threads:[~2003-07-17 13:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 13:11 gbeauchesne at mandrakesoft dot com [this message]
2003-07-17 13:13 ` [Bug optimization/11559] " gbeauchesne at mandrakesoft dot com
2003-07-17 13:13 ` gbeauchesne at mandrakesoft dot com
2003-07-17 13:16 ` aj at gcc dot gnu dot org
2003-07-17 20:13 ` zlomek at gcc dot gnu dot org
2003-07-18  4:49 ` cvs-commit at gcc dot gnu dot org
2004-04-21  1:27 ` pinskia 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=20030717131115.11559.gbeauchesne@mandrakesoft.com \
    --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).