public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10805: [sun-solaris2.7] relocation error when creating sparcv9/libgcc_s.so.1 Date: Fri, 16 May 2003 15:16:00 -0000 [thread overview] Message-ID: <20030516151600.1163.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10805; it has been noted by GNATS. From: Eric Botcazou <ebotcazou@libertysurf.fr> To: Marc Glisse <marc.glisse@ens.fr> Cc: <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: bootstrap/10805: [sun-solaris2.7] relocation error when creating sparcv9/libgcc_s.so.1 Date: Fri, 16 May 2003 17:11:49 +0200 > One difference is that I do not have this patch. I will try to install it > as soon as I can. For the bootstrap compiler, I used: > cc: Sun WorkShop 6 2000/04/07 C 5.1 > gcc (GCC) 3.2.2 > > And both give the same result. Steven Christensen tried with GCC 3.2.3 too and same result. > > 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. > > first there is a lot of gcc. Then this gcc/xgcc. Actually this should be > clearer: > > make[3]: *** [sparcv9/libgcc_s_sparcv9.so] Error 1 > make[3]: Leaving directory `/global/lavarenne/download/gcc-3.3/gcc' > make[2]: *** [stmp-multilib] Error 2 > make[2]: Leaving directory `/global/lavarenne/download/gcc-3.3/gcc' > make[1]: *** [stage1_build] Error 2 > make[1]: Leaving directory `/global/lavarenne/download/gcc-3.3/gcc' > make: *** [bootstrap] Error 2 Ok, it's stage1. Given that we have the same problem with 3 different bootstrap compilers, I'm inclined to suspect the Sun assembler. > With the messages: > > ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: > symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned > > ld: fatal: relocation error: R_SPARC_64: file libgcc/sparcv9/_muldi3.o: > symbol <unknown>: offset 0xffffffff7ec133eb is non-aligned > > ld: fatal: relocation error: R_SPARC_64: file libgcc/sparcv9/_muldi3.o: > symbol <unknown>: offset 0xffffffff7ec133f3 is non-aligned > > ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: > symbol <unknown>: offset 0xffffffff7ec13867 is non-aligned > > ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: > symbol <unknown>: offset 0xffffffff7ec14a2f is non-aligned > > But about all the .o give this kind of messages. I think the relocations type R_SPARC_32 and R_SPARC_64 are wrong here because the offsets are rightfully unaligned. The same dump on my Solaris 7 box shows only R_SPARC_UA32 and R_SPARC_UA64 types which are described by the Sun docs as follows: R_SPARC_UA32 This relocation type resembles R_SPARC_32, except that it refers to an unaligned word. That is, the word to be relocated must be treated as four separate bytes with arbitrary alignment, not as a word aligned according to the architecture requirements. -- Eric Botcazou
next reply other threads:[~2003-05-16 15:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 15:16 Eric Botcazou [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 13:16 Marc Glisse 2003-05-16 13:06 Eric Botcazou 2003-05-16 10:08 ebotcazou 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=20030516151600.1163.qmail@sources.redhat.com \ --to=ebotcazou@libertysurf.fr \ --cc=gcc-prs@gcc.gnu.org \ --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: 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).