public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65778] v8 build fails with assembly error with LTO enabled on arm-linux-gnueabihf
Date: Wed, 22 Apr 2015 18:49:00 -0000 [thread overview]
Message-ID: <bug-65778-4-UR4SlYVJQd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65778-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65778
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ramana at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #3 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Can't you not use just a move instead of a ldr here? basically it is the
> assembler which creates the constant pool here and that is too far from the
> where the ldr is located because the function is "huge".
Indeed the compiler has no role here.
It's not like __ARM_NR_cacheflush is going to change is it ? You can write it
similar to the libgcc implementation for clear_cache.
regards
Ramana
prev parent reply other threads:[~2015-04-22 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 21:28 [Bug lto/65778] New: " prathamesh3492 at gcc dot gnu.org
2015-04-15 23:35 ` [Bug lto/65778] " pinskia at gcc dot gnu.org
2015-04-16 7:40 ` rguenth at gcc dot gnu.org
2015-04-22 18:49 ` ramana at gcc dot gnu.org [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=bug-65778-4-UR4SlYVJQd@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).