public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, glisse@sequoia.ens.fr,
	nobody@gcc.gnu.org
Subject: Re: bootstrap/10805: [sun-solaris2.7] relocation error when creating sparcv9/libgcc_s.so.1
Date: Fri, 16 May 2003 10:08:00 -0000	[thread overview]
Message-ID: <20030516100800.9539.qmail@sources.redhat.com> (raw)

Synopsis: [sun-solaris2.7] relocation error when creating sparcv9/libgcc_s.so.1

State-Changed-From-To: open->feedback
State-Changed-By: ebotcazou
State-Changed-When: Fri May 16 10:07:59 2003
State-Changed-Why:
    I can't reproduce on SunOS vegeta 5.7 Generic_106541-23 sun4u sparc SUNW,Ultra-2
    with cc: Sun WorkShop 6 update 2 C 5.3 Patch 111679-08 2002/05/09
    as the bootstrap compiler.
    
    Could you determine at which stage bootstrap fails?
    If the compiler's C source files were latterly compiled by cc, it's stage1.
    If they were compiled by stage1/xgcc, it's stage2 and if they were
    compiled by stage2/xgcc, it's stage3.
    
    And could you post the ouput of 'dump -r _muldi3.o'?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10805


             reply	other threads:[~2003-05-16 10:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 10:08 ebotcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-21  8:57 ebotcazou
2003-05-20 18:46 Marc Glisse
2003-05-20 12:08 Eric Botcazou
2003-05-20 11:26 Marc Glisse
2003-05-20 10:56 Eric Botcazou
2003-05-17  7:06 Eric Botcazou
2003-05-17  6:42 ebotcazou
2003-05-17  1:16 Dara Hazeghi
2003-05-16 22:26 Eric Botcazou
2003-05-16 15:16 Eric Botcazou
2003-05-16 13:16 Marc Glisse
2003-05-16 13:06 Eric Botcazou
2003-05-15 17:06 glisse

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=20030516100800.9539.qmail@sources.redhat.com \
    --to=ebotcazou@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=glisse@sequoia.ens.fr \
    --cc=nobody@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).