public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rickert@cs.niu.edu
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/4254: gcc-3.0 will not build on Solaris 9 (beta) in x86 architecture
Date: Thu, 06 Sep 2001 17:16:00 -0000	[thread overview]
Message-ID: <20010907000811.30750.qmail@sourceware.cygnus.com> (raw)

>Number:         4254
>Category:       bootstrap
>Synopsis:       gcc-3.0 will not build on Solaris 9 (beta) in x86 architecture
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 06 17:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Neil Rickert, Northern Illinois University
>Release:        gcc-3.0
>Organization:
>Environment:

>Description:
/export/home/rickert/gcc-3.0/gcc/unwind-dw2.c:1103: warning: implicit declaratio
n of function `memcpy'
Assembler: unwind-dw2.c
        "/var/tmp/ccaekfib.s", line 4259 : Illegal subtraction
        "/var/tmp/ccaekfib.s", line 4282 : Illegal subtraction
        "/var/tmp/ccaekfib.s", line 4313 : Illegal subtraction

This occurs during the second stage build.  It occurs
whether compiling with the Sun workshop compiler, or
with gcc-2.95.2

A full transcript is available on request (until I decide
to delete it).

      -----------

Somewhat related.  gcc-2.95.2 also failed to build
when using the Sun workshop compilers -- this was
a compare fail between stage 2 and stage 3 object files.

However gcc-2.8.1 built fine.  When using that,
gcc-2.95.2 also built fine.
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2001-09-06 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 17:16 rickert [this message]
2001-09-09 18:33 aoliva

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=20010907000811.30750.qmail@sourceware.cygnus.com \
    --to=rickert@cs.niu.edu \
    --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).