public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: sirl@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/6569: sparc-sun-solaris2.7 C testsuite regression in compile/20011119-2.c
Date: Tue, 07 May 2002 06:16:00 -0000	[thread overview]
Message-ID: <20020507131604.904.qmail@sources.redhat.com> (raw)

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

From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: davem@gcc.gnu.org,davem@redhat.com,gcc-bugs@gcc.gnu.org,
 gcc-gnats@gcc.gnu.org,gcc-prs@gcc.gnu.org,jakub@redhat.com,
 mark@codesourcery.com,nobody@gcc.gnu.org,rth@redhat.com
Subject: Re: target/6569: sparc-sun-solaris2.7 C testsuite regression
  in compile/20011119-2.c
Date: Tue, 07 May 2002 15:14:49 +0200

 At 14:45 07.05.2002, Kaveh R. Ghazi wrote:
 >  > From: Mark Mitchell <mark@codesourcery.com>
 >  >
 >  > >> Can you try the attached patch? It seems to work for me, but the
 >  > >> bootstrap hasn't completed yet. While I was at it, I improved the
 >  > >> placing of the warning messages. I'm still a bit confused, cause it
 >  > >> sometimes seems olddecl and newdecl appeared to be swapped compared to
 >  > >> their sourcefile ordering.
 >  > >
 >  > > FYI, bootstrap+regtest on x86-linux-gnu completed successfully.
 >  >
 >  > OK; once you have confirmation of the SPARC results go ahead and check it
 >  > in.
 >
 >Unfortunately, the patch did not solve the problem listed in the PR.
 >I still get the same 'as' errors from compile/20011119-2.c
 >
 >compile/20011119-2.c:3: warning: weak declaration of `foo' after first use 
 >results in unspecified behavior
 >/usr/ccs/bin/as: "/var/tmp//ccQOIg1d.s", line 51: error: invalid operand
 >--------------------------------------------------^^^^^
 
 Yeah, I managed to get access to a solaris-2.8 machine, even though I 
 wasn't able to bootstrap with Solaris as/ld (see below), I was able to 
 reproduce the failure. Re-checking on x86-linux-gnu revealed that it even 
 doesn't fix the problem there, so I must have mixed something up yesterday. 
 Frankly, I'm a bit at a loss here, cause I've tried several strategies 
 yesterday and they either didn't fix the testcase or caused some of the 
 weak tests to fail. Especially I tried to use the TREE_USED flag of the 
 WEAK_DECLS TREE_LIST to mark when a weak already had been assembled, but it 
 didn't work out :-(. I seem to misunderstand something about how the tree 
 structures are handled.
 
 Franz.
 
 PS:
 The bootstrap failure with solaris-2.8 as/ld and configured with:
 
           --enable-shared \
           --enable-threads \
           --with-system-zlib \
           --with-libiconv-prefix=/usr/local \
           sparc-sun-solaris2.8
 
 This results in:
 
 ...
 strcpy                              0x42c 
 .libs/libstdc++.lax/libsupc++convenience.a/dyn-string.o
 strdup                              0x694 
 .libs/libstdc++.lax/libsupc++convenience.a/cxa_demangle.o
 __iob                               0x45e8 
 .libs/libstdc++.lax/libsupc++convenience.a/cxa_demangle.o
 __iob                               0x4634 
 .libs/libstdc++.lax/libsupc++convenience.a/cxa_demangle.o
 __iob                               0x4644 
 .libs/libstdc++.lax/libsupc++convenience.a/cxa_demangle.o
 __iob                               0x4654 
 .libs/libstdc++.lax/libsupc++convenience.a/cxa_demangle.o
 ld: fatal: relocations remain against allocatable but non-writable sections
 collect2: ld returned 1 exit status
 make[4]: *** [libstdc++.la] Error 1
 make[4]: Leaving directory 
 `/home/gnu/obj/gcc31/sparc-sun-solaris2.8/libstdc++-v3/src'
 


             reply	other threads:[~2002-05-07 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07  6:16 Franz Sirl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-08  7:49 mmitchel
2002-05-07  8:36 Franz Sirl
2002-05-07  7:47 mmitchel
2002-05-07  7:46 Mark Mitchell
2002-05-07  5:56 Kaveh R. Ghazi
2002-05-06 15:46 Mark Mitchell
2002-05-06 15:36 Franz Sirl
2002-05-05 23:03 davem
2002-05-05 21:56 ghazi

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=20020507131604.904.qmail@sources.redhat.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=sirl@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).