public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bule1 at huawei dot com" <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 08:09:04 +0000	[thread overview]
Message-ID: <bug-95285-4-78CCFH3G6F@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 #6 from Bu Le <bule1 at huawei dot com> ---
(In reply to Wilco from comment #4)
> (In reply to Bu Le from comment #3)
> > (In reply to Wilco from comment #2)

> Well the question is whether we're talking about more than 4GB of code or
> more than 4GB of data. With >4GB code you're indeed stuck with the large
> model. With data it is feasible to automatically use malloc for arrays when
> larger than a certain size, so there is no need to change the application at
> all. Something like that could be the default in the small model so that you
> don't have any extra overhead unless you have huge arrays. Making the
> threshold configurable means you can tune it for a specific application.


Is this automatic malloc already avaiable on some target? I haven't found an
example that works in that way. Would you mind provide an example?

  parent reply	other threads:[~2020-05-27  8:09 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 [this message]
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
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-78CCFH3G6F@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).