public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: donnte@microsoft.com To: gcc-gnats@gcc.gnu.org Subject: optimization/6864: Optimizer infinite loop/memory runaway (on gdb sources) Date: Wed, 29 May 2002 18:53:00 -0000 [thread overview] Message-ID: <20020529235339.12000.qmail@sources.redhat.com> (raw) >Number: 6864 >Category: optimization >Synopsis: Optimizer infinite loop/memory runaway (on gdb sources) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed May 29 16:56:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: donnte@microsoft.com >Release: 3.2 20020528 (experimental) >Organization: >Environment: Interix. >Description: Goto in switch (presumably) confuses live register calculation. Attached sample code, with marked goto (the only goto) turned on drives the compiler into an infinite loop (eating memory) at about 1145 in flow.c. (See "while (qhead != qtail)".) Removing the goto causes the compiler to terminate normally (but of course the code is incorrect.) The problem appeared between 5/10 and 5/28. Sample code is somewhat stripped down from the original gdb source, removing irrelevant functions. Both the code before the switch and (obviously) the switch body are needed to repro. (This is all post-preprocessor, but a .c file for easy use of comments and #if for minimization.) >How-To-Repeat: Compile attached file, command line: /dev/fs/C/home/donn.intel/gnu2.intel/local_bin/gcc -B/dev/fs/C/home/donn.intel/gnu2.intel/local_bin/ -c -g -O2 -D_ALL_SOURCE -implicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized test.c -v --save-temps >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-29 23:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-29 18:53 donnte [this message] 2002-12-02 13:38 bangerth 2002-12-02 14:21 bangerth 2002-12-02 14:26 Donn Terry
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=20020529235339.12000.qmail@sources.redhat.com \ --to=donnte@microsoft.com \ --cc=gcc-gnats@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: linkBe 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).