public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baratharon at caesar dot elte.hu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94236] -mcmodel=large does not work on aarch64
Date: Mon, 23 Mar 2020 07:24:31 +0000	[thread overview]
Message-ID: <bug-94236-4-Euno4DlGCU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94236-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94236

--- Comment #7 from Aron <baratharon at caesar dot elte.hu> ---
(In reply to Andrew Pinski from comment #6)
> Note for Threos OS, please don't reuse the same target triplet as elf or
> linux; use your own triplet.  Also adding long calls is not hard and such.

As a simple start, I used the -ffreestanding -nostdlib -nostdinc combination,
but they did not made any difference on the output object file, so I removed
them in post #1. On x86_64 and armv7 we already have target (cross) gcc, but we
just started to work on aarch64. Either Linux target or Threos target, CALL26
would be also an issue. It seems, I have to mock with the target gcc first
before we can ran anything on the HW to include the long calls patch. Still, I
would be happy if the mainline gcc have the -mlong-calls for aarch64.

  parent reply	other threads:[~2020-03-23  7:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 15:42 [Bug c/94236] New: " baratharon at caesar dot elte.hu
2020-03-20 16:08 ` [Bug target/94236] " pinskia at gcc dot gnu.org
2020-03-20 16:17 ` pinskia at gcc dot gnu.org
2020-03-20 16:19 ` baratharon at caesar dot elte.hu
2020-03-20 16:25 ` pinskia at gcc dot gnu.org
2020-03-23  7:11 ` baratharon at caesar dot elte.hu
2020-03-23  7:15 ` pinskia at gcc dot gnu.org
2020-03-23  7:24 ` baratharon at caesar dot elte.hu [this message]
2020-03-23 10:56 ` rearnsha at gcc dot gnu.org
2021-01-25 20:17 ` wilco 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-94236-4-Euno4DlGCU@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).