public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@albatross.co.nz>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: gcj build on Itanium
Date: Tue, 27 Feb 2001 02:32:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005214@msgid-missing> (raw)

"Boehm, Hans" wrote:

> Problem 2: The build process had trouble finding the libgcc_s.so.0 it just
> built.
>
> Workaround: I hacked in the right linker option.
>
> Request: Could someone fix this properly, if it is indeed just a build
> problem.

I fixed this about a week ago (unless its a new problem).

> Problem 3: Finally clauses are now miscompiled by the Itanium gcj.  The code
> generates references to undefined labels, as in "addl r14=@ltoff(.L837),gp"
> with no definition of .L837.

This sounds similar to the PR java/2095 reported on Solaris. It probably
affects multiple platforms (maybe just SJLJ ones?). It probably doesn't affect
the branch.

> Problem 5: Static linking tends to result in "eh.o...: undefined reference
> to `fwrite'.  This seems to be a library ordering problem, which might also
> affect other platforms.
>
> Workaround: use "-u fwrite" on the command line.

> Request: What's a proper fix?

Good question. This has been happening since around about when we changed to
the shared libgcc. Maybe the compiler just needs to add an implicit "-u fwrite"
when static linking? I don't know why c++ works and gcj doesn't though.

regards

  [ bryce ]




                 reply	other threads:[~2001-02-27  2:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590693005214@msgid-missing \
    --to=bryce@albatross.co.nz \
    --cc=linux-ia64@vger.kernel.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