public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Simon Stelling <blubb@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] -fPIC - Toolchain broken?
Date: Wed, 18 Oct 2006 20:32:59 +0200	[thread overview]
Message-ID: <4536735B.3080301@gentoo.org> (raw)
In-Reply-To: <4536675E.5070901@getdesigned.at>

Sebastian Redl wrote:
> Anyway, just so I understand: the function is inline/static (don't know
> which of these causes the problem) which causes compareRanges to be
> exported, but not compiled position-independently. The linker, seeing
> that, fails. But with -O>1, it somehow doesn't actually export the
> function or something like that, and thus it works?

I didn't dig any deeper then what I have written already for icu as we 
have another test case provided in bug 151832. Basically gcc shouldn't 
inline the function or at least provide a callable symbol because its 
address is used later on (in the same file, even), which is what we 
found in the gcc documentation but not in the code ;)

So yes, it IS a toolchain-bug, but one the gcc-4.1 users share (gcc 3.4 
works correctly apparently) :D

[1] http://bugs.gentoo.org/show_bug.cgi?id=151832

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 developer
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-10-18 18:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:08 [gentoo-amd64] -fPIC - Toolchain broken? Sebastian Redl
2006-10-18 15:28 ` Hemmann, Volker Armin
2006-10-18 15:53 ` Simon Stelling
2006-10-18 16:08   ` Simon Stelling
2006-10-18 17:41   ` Sebastian Redl
2006-10-18 18:32     ` Simon Stelling [this message]
2006-10-18 21:21 ` [gentoo-amd64] " Duncan
2006-10-19  9:54   ` Sebastian Redl
2006-10-19 13:11     ` Conway S. Smith
2006-10-19 15:42       ` Simon Stelling
2006-10-19 20:43         ` Duncan
2006-10-20  9:10           ` Simon Stelling
2006-10-23 14:20           ` Kevin F. Quinn
2006-10-23 15:22             ` Duncan
2006-10-19 20:33     ` Duncan

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=4536735B.3080301@gentoo.org \
    --to=blubb@gentoo.org \
    --cc=gentoo-amd64@lists.gentoo.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