public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Witold Baryluk" <baryluk@smp.if.uj.edu.pl>
To: Richard Henderson <rth@twiddle.net>
Cc: Michael Cree <mcree@orcon.net.nz>,
	debian-alpha@lists.debian.org,  binutils@sourceware.org
Subject: Re: Problems with linker on Alpha
Date: Thu, 05 May 2011 20:17:00 -0000	[thread overview]
Message-ID: <20110505201649.GD18523@smp.if.uj.edu.pl> (raw)
In-Reply-To: <4DBF055E.1070701@twiddle.net>

[-- Attachment #1: Type: text/plain, Size: 3693 bytes --]

On 05-02 12:26, Richard Henderson wrote:
> On 04/30/2011 07:25 PM, Michael Cree wrote:
> > First off is bug 12608 [1] which I believe I have identified the
> > problem and have posted a patch to the bug tracker.  I am hoping that
> > if it is acceptable that you can commit it.
> 
> I'll have a look.
> 
> > Secondly, I noted a number of test suite failures in the ld component
> > while building binutils.  Some of them are with plugins which might
> > explain why bugs/crashes seem to randomly appear and disappear with
> > larger software packages using plugins. I would like to investigate
> > the test suite failures but am yet to understand the automated system
> > using expect and isolate each test so that I can run them manually.
> > Are you able to give me a bit of guidance on that?
> 
> "Large number"?  I get
> 
>                 === binutils Summary ===
> 
> # of expected passes            81
> # of unsupported tests          2
> Host   is x86_64-unknown-linux-gnu
> 
>                 === gas Summary ===
> 
> # of expected passes            132
> # of expected failures          1
> # of unsupported tests          1
> Host   is x86_64-unknown-linux-gnu
> 
>                 === ld tests ===
> 
> Running target alpha-qemu
> FAIL: plugin claimfile lost symbol
> FAIL: plugin claimfile replace symbol
> FAIL: plugin claimfile resolve symbol
> XPASS: Preserve default . = 0
> XPASS: Preserve explicit . = 0
> 
>                 === ld Summary ===
> 
> # of expected passes            278
> # of unexpected failures        3
> # of unexpected successes       2
> # of expected failures          7
> 
> That plugin test, as far as I know, isn't system specific and fails
> for all targets.
> 
> > Thirdly, a number of large C++ programs (such as firefox/xulrunner,
> > webkit, libreoffice) bomb out with GPREL16 relocation truncation
> > errors when using the -relax option but link successfully when using
> > --no-relax.  I have reopened bug 5276 [2] which describes this
> > problem.  It would be nice to get this problem fixed!
> 
> Yeah.  Uros just reported this same problem with gcc itself.
> 
> Also, I'm aware of an ld -relax bug that causes the Linux kernel
> to be mis-compiled.  Thankfully at the moment the default is to
> not apply relaxation during the kernel link.
> 
> > Fourthly, the Debian supplied gcc-4.6 fails to build on Debian
> > because of a boostrap comparison failure, so I attempted to build
> > upstream gcc-4.6 branch source which got past the bootstrap
> > comparison but failed later on with the following error:
> > 
> > /usr/bin/ld: BFD (GNU Binutils for Debian) 2.21.51.20110419 internal error, aborting at ../../bfd/elf64-alpha.c line 2064 in elf64_alpha_gc_sweep_hook

I'm now also comiling vanila gcc-4.6.0 on both unstable as well lenny to see if this is a regression
in binutils or other components.

> > 
> > when linking libstdc++.  This is using the Debian supplied bintuils
> > version 2.21.51.20110419-2, also with my patch to fix the TLS issue.
> > Maybe I should make a bug entry for it.
> 
> Yes, please to enter a bug for it.  I hadn't seen this one before,
> possibly because I've been cheating and only building C.
> 
> I've been working on getting QEMU working for alpha-softmmu recently,
> hoping to be able to debug some of the alpha problems that have been
> creeping in "natively".

Hi, thanks into looking into alpha issues.

As of QEMU i must say "Cool!".
I was going to work on qemu-alpha after fixing linker and compiler issue
in current versions. Is there any repository for you work?

Regards,
Witek

-- 
Witold Baryluk

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2011-05-05 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01  2:25 Michael Cree
2011-05-02 19:26 ` Richard Henderson
2011-05-03  0:32   ` Alan Modra
2011-05-29  3:37     ` Michael Cree
2011-05-30 10:58       ` Alan Modra
2011-05-31  4:28         ` Richard Henderson
2011-05-03  9:21   ` Michael Cree
2011-05-03 10:12     ` Michael Cree
2011-05-06 10:25     ` Michael Cree
2011-05-06 14:08       ` Richard Henderson
2011-05-29  3:48         ` Michael Cree
2011-05-05 20:17   ` Witold Baryluk [this message]

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=20110505201649.GD18523@smp.if.uj.edu.pl \
    --to=baryluk@smp.if.uj.edu.pl \
    --cc=binutils@sourceware.org \
    --cc=debian-alpha@lists.debian.org \
    --cc=mcree@orcon.net.nz \
    --cc=rth@twiddle.net \
    /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).