public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at false dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/2675] arm-none-eabi-linux-gnueabi doesn't build
Date: Fri, 19 May 2006 19:27:00 -0000 [thread overview]
Message-ID: <20060519192705.5834.qmail@sourceware.org> (raw)
In-Reply-To: <20060519183843.2675.kazu@gcc.gnu.org>
------- Additional Comments From drow at false dot org 2006-05-19 19:27 -------
Subject: Re: arm-none-eabi-linux-gnueabi doesn't build
On Fri, May 19, 2006 at 07:22:53PM -0000, roland at gnu dot org wrote:
> There is no reason in general that function should not be inlined.
> It really should be inlined. Perhaps you can find a fix for the arm build that
> does not deoptimize the code.
Then I'll mark it non-inlined in an ARM copy; but I expect this to
cause problems on many other targets. It only materializes on very
recent versions of GCC, because previously we used -fno-unit-at-a-time
which suppressed the "inline static functions called once"
optimization; if GCC is new enough we use -fno-toplevel-reorder
instead.
Sedding GCC's assembly output has historically worked "well enough" for
simple calls to known static functions, but it's not surprising that
call_gmon_start requires a constant pool. I expect to see similar
problems at least for SH.
Anyway, you want an ARM-only fix, you'll get one :-) I'll take care of
it.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2675
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-05-19 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 18:38 [Bug libc/2675] New: " kazu at gcc dot gnu dot org
2006-05-19 18:58 ` [Bug ports/2675] " roland at gnu dot org
2006-05-19 19:04 ` drow at sources dot redhat dot com
2006-05-19 19:23 ` roland at gnu dot org
2006-05-19 19:27 ` drow at false dot org [this message]
2006-10-31 15:05 ` drow at sources dot redhat dot com
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=20060519192705.5834.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).