public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david.abdurachmanov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63304] Aarch64 pc-relative load offset out of range Date: Mon, 05 Jan 2015 10:27:00 -0000 [thread overview] Message-ID: <bug-63304-4-Xamw63ZsIx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63304-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63304 --- Comment #12 from David Abdurachmanov <david.abdurachmanov at gmail dot com> --- I decided to re-enable -Os for OpenLoops. Then use powerful hardware with 32-physical-cores (x86_64) and 0.5TB of RAM to see if I could get lucky. Fired up QEMU user mode with Fedora for AArch64 chroot for compiling. It did resolve some of failures, but not everything. I have seen processes going as far as 25+GB of RSS and taking hours to finish. This is the reason package is compiled with -O0.
next prev parent reply other threads:[~2015-01-05 10:27 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-19 5:31 [Bug target/63304] New: " venkataramanan.kumar at amd dot com 2014-09-19 5:38 ` [Bug target/63304] " venkataramanan.kumar at amd dot com 2014-09-19 5:44 ` venkataramanan.kumar at amd dot com 2014-09-19 7:56 ` pinskia at gcc dot gnu.org 2014-09-19 10:19 ` rearnsha at gcc dot gnu.org 2014-09-19 14:09 ` venkataramanan.kumar at amd dot com 2014-09-19 15:02 ` rearnsha at gcc dot gnu.org 2014-09-19 17:58 ` venkataramanan.kumar at amd dot com 2014-09-19 18:00 ` pinskia at gcc dot gnu.org 2014-10-12 0:42 ` pinskia at gcc dot gnu.org 2014-10-12 2:40 ` pinskia at gcc dot gnu.org 2014-12-28 20:15 ` david.abdurachmanov at gmail dot com 2015-01-05 10:27 ` david.abdurachmanov at gmail dot com [this message] 2015-01-10 11:24 ` david.abdurachmanov at gmail dot com 2015-07-20 9:42 ` pinskia at gcc dot gnu.org 2015-07-20 12:58 ` wdijkstr at arm dot com 2015-07-22 16:06 ` ramana at gcc dot gnu.org 2015-07-27 14:34 ` ramana at gcc dot gnu.org 2015-07-29 10:51 ` ramana at gcc dot gnu.org 2015-07-29 11:19 ` david.abdurachmanov at gmail dot com 2015-07-30 8:02 ` ramana at gcc dot gnu.org 2015-08-07 11:29 ` david.abdurachmanov at gmail dot com 2015-09-11 9:45 ` ramana at gcc dot gnu.org 2015-09-14 13:17 ` ramana at gcc dot gnu.org 2015-10-09 10:58 ` ramana at gcc dot gnu.org 2015-10-09 11:02 ` ramana at gcc dot gnu.org 2015-10-09 11:08 ` ramana at gcc dot gnu.org 2015-10-22 4:27 ` ramana at gcc dot gnu.org
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-63304-4-Xamw63ZsIx@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: linkBe 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).