public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: etienne.lorrain@masroudeau.com
To: gcc-gnats@gcc.gnu.org
Subject: c/6245: GCC-3.0.4 infinite loop on invalid code
Date: Wed, 10 Apr 2002 03:06:00 -0000	[thread overview]
Message-ID: <20020410100207.28657.qmail@sources.redhat.com> (raw)


>Number:         6245
>Category:       c
>Synopsis:       GCC-3.0.4 infinite loop on invalid code
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 10 03:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Etienne Lorrain
>Release:        GCC-3.0.4
>Organization:
>Environment:
Linux
>Description:
Continually display, until ^C:
bug.c:19: initializer element is not constant
bug.c:19: (near initialization for `STATE')
>How-To-Repeat:
[etienne@nextstar gujin]$ /home/etienne/projet/toolchain/bin/gcc -v
Reading specs from /home/etienne/projet/toolchain/lib/gcc-lib/i686-pc-linux-gnu/3.0.4/specs
Configured with: ../configure --prefix=/home/etienne/projet/toolchain --enable-languages=C
Thread model: single
gcc version 3.0.4
[etienne@nextstar gujin]$ cat bug.c
extern unsigned _srodata[], _edata[];

extern const struct state_str {
    unsigned dummy_but_needed_for_bug;
    struct short_bound_str {
        signed short low_limit;
        signed short high_limit;
        } __attribute__ ((packed)) stack_limit;
    struct long_bound_str {
        signed  low_limit;
        signed  high_limit;
        } __attribute__ ((packed)) data_limit;
    const char *BoundMsg;
    } STATE;

const struct state_str STATE = {
    data_limit: { low_limit: (unsigned)_srodata , high_limit: 0xFFFF },
    stack_limit: { low_limit: (short)_edata, high_limit: 0xFFFC },
    };
[etienne@nextstar gujin]$ /home/etienne/projet/toolchain/bin/gcc bug.c
   .... (cannot catch beginning) ...
bug.c:19: (near initialization for `STATE')
bug.c:19: initializer element is not constant
bug.c:19: (near initialization for `STATE')
bug.c:19: initializer element is not constant
bug.c:19: (near initialization for `STATE')
bug.c:19: initializer element is not constant
bug.c:19: (near initialization for `STATE')
bug.c:19: initializer element is not constant
bug.c:19: (near initialization for `STATE')
bug.c:19: initializer element is not constant
 ....
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-10 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10  3:06 etienne.lorrain [this message]
2002-04-14 13:50 jakub
2003-02-17 15:32 bangerth

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=20020410100207.28657.qmail@sources.redhat.com \
    --to=etienne.lorrain@masroudeau.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: 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).