public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95285] AArch64:aarch64 medium code model proposal
Date: Wed, 27 May 2020 12:48:57 +0000	[thread overview]
Message-ID: <bug-95285-4-UL1W3B1suC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95285-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Bu Le from comment #10)
> > Fortran already has -fstack-arrays to decide between allocating arrays on
> > the heap or on the stack.
> 
> I tried the flag with my example. The fstack-array seems cannot move the
> array in the bss to the heap. The problem is still there. 

It is an existing feature that chooses between malloc and stack. It would need
modification to do the same for large data/bss objects.

> Anyway, my point is that the size of single data does't affact the fact that
> medium code model is missing in aarch64 and aarch64 is lack of PIC large
> code model.

What is missing is efficient support for >4GB of data, right? How that is
implemented is a different question - my point is that it does not require a
new code model. It would be much better if it just worked without users even
needing to think about code models.

Also, what is the purpose of a large fpic model? Are there any applications
that use shared libraries larger than 4GB?

  parent reply	other threads:[~2020-05-27 12:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23  6:40 [Bug target/95285] New: " bule1 at huawei dot com
2020-05-23  6:45 ` [Bug target/95285] " bule1 at huawei dot com
2020-05-26 13:14 ` wilco at gcc dot gnu.org
2020-05-26 13:42 ` bule1 at huawei dot com
2020-05-26 14:11 ` wilco at gcc dot gnu.org
2020-05-26 15:05 ` wilco at gcc dot gnu.org
2020-05-27  8:09 ` bule1 at huawei dot com
2020-05-27  9:17 ` bule1 at huawei dot com
2020-05-27  9:43 ` wilco at gcc dot gnu.org
2020-05-27 10:19 ` wilco at gcc dot gnu.org
2020-05-27 12:05 ` bule1 at huawei dot com
2020-05-27 12:38 ` bule1 at huawei dot com
2020-05-27 12:48 ` wilco at gcc dot gnu.org [this message]
2020-05-27 13:05 ` wilco at gcc dot gnu.org
2020-05-27 13:19 ` bule1 at huawei dot com
2020-05-28 13:23 ` wilco at gcc dot gnu.org
2020-12-10 13:56 ` wdijkstr at arm dot com
2021-09-10 10:35 ` wilco at gcc dot gnu.org
2021-09-11  2:00 ` pinskia 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-95285-4-UL1W3B1suC@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).