public inbox for
help / color / mirror / Atom feed
From: Dara Hazeghi <>
Subject: Re: target/9945: [x86 -> mn10020] ultra trivial file (10 lines) causes internal compiler error
Date: Thu, 15 May 2003 00:36:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR target/9945; it has been noted by GNATS.

From: Dara Hazeghi <>
Subject: Re: target/9945: [x86 -> mn10020] ultra trivial file (10 lines) causes internal compiler error
Date: Wed, 14 May 2003 17:32:50 -0700 
 well given that mn10200-elf is an obsolete target, and will be removed  
 from gcc 3.4, I'm not too surprised. Anyhow, gcc 3.3 won't even go so  
 far as to build cc1:
 /usr/bin/gcc -c   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall  
 -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional  
 -pedantic -Wno-long-long   -DHAVE_CONFIG_H -DGENERATOR_FILE    -I. -I.  
 -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config  
 -I../../gcc/gcc/../include insn-conditions.c
 insn-conditions.c:89: braced-group within expression allowed only  
 inside a function
 insn-conditions.c:89: request for member `rtx' in something not a  
 structure or union
 insn-conditions.c:89: initializer element is not constant
 insn-conditions.c:89: (near initialization for  
 insn-conditions.c:89: parse error before ')' token
 insn-conditions.c:89: `__s2_len' undeclared here (not in a function)
 insn-conditions.c:89: warning: excess elements in struct initializer
 So it doesn't look like this bug will get fixed anytime soon.

             reply	other threads:[~2003-05-15  0:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  0:36 Dara Hazeghi [this message]
2003-05-15  4:30 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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