public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: LuluCheng <chenglulu@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6353] LoongArch: Change the value of macro TRY_EMPTY_VM_SPACE from 0x8000000000 to 0x1000000000.
Date: Mon, 27 Feb 2023 01:07:24 +0000 (GMT)	[thread overview]
Message-ID: <20230227010724.98DEA3858D1E@sourceware.org> (raw)

https://gcc.gnu.org/g:529e03b9882fe48cfa3c182abb12a5858a5762a2

commit r13-6353-g529e03b9882fe48cfa3c182abb12a5858a5762a2
Author: Lulu Cheng <chenglulu@loongson.cn>
Date:   Mon Feb 20 16:47:11 2023 +0800

    LoongArch: Change the value of macro TRY_EMPTY_VM_SPACE from 0x8000000000 to 0x1000000000.
    
    The PCH mechanism first tries to map the .gch file to the virtual memory
    space pointed to by TRY_EMPTY_VM_SPACE during the compilation process.
    
    The original value of TRY_EMPTY_VM_SPACE macro is 0x8000000000,
    but like la464 only has 40 bits of virtual address space, this value
    just exceeds the address range.
    
    If we want to support chips with less than 40 bits virtual addresses,
    then the value of this macro needs to be set small. I think setting
    this value small will increase the probability of virtual address
    mapping failure. And the purpose of pch is to make compilation faster,
    but I think we rarely compile on embedded systems. So this situation
    may not be within our consideration.
    
    So change the value of this macro to 0x1000000000.
    
    gcc/ChangeLog:
    
            * config/host-linux.cc (TRY_EMPTY_VM_SPACE): Modify the value of
            the macro to 0x1000000000.

Diff:
---
 gcc/config/host-linux.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/host-linux.cc b/gcc/config/host-linux.cc
index a891651a7b6..d1aa7ab28ca 100644
--- a/gcc/config/host-linux.cc
+++ b/gcc/config/host-linux.cc
@@ -99,7 +99,7 @@
 #elif defined(__riscv) && defined (__LP64__)
 # define TRY_EMPTY_VM_SPACE	0x1000000000
 #elif defined(__loongarch__) && defined(__LP64__)
-# define TRY_EMPTY_VM_SPACE	0x8000000000
+# define TRY_EMPTY_VM_SPACE	0x1000000000
 #else
 # define TRY_EMPTY_VM_SPACE	0
 #endif

                 reply	other threads:[~2023-02-27  1:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230227010724.98DEA3858D1E@sourceware.org \
    --to=chenglulu@gcc.gnu.org \
    --cc=gcc-cvs@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).