public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gang.peng at aclsemi dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/115485] CASEServer.cpp:203:1: internal compiler error: in require_pic_register, at config/arm/arm.c:7855
Date: Fri, 14 Jun 2024 05:59:06 +0000	[thread overview]
Message-ID: <bug-115485-4-gEFekWY3aV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115485-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Gang Peng <gang.peng at aclsemi dot com> ---
Dear Sir,

When I build cpp with gcc-arm-none-eabi-10.3-2021.10/bin/arm-none-eabi-g++
I meet this error, and the following compilation options are required：

CFLAGS += -fPIE
CFLAGS += -msingle-pic-base
CFLAGS += -mpic-register=r9
CFLAGS += -fomit-frame-pointer
CFLAGS += -mno-pic-data-is-text-relative
CFLAGS += -mthumb
CFLAGS += -mlong-calls 

Could you kindly help to have a look how I should solve this problem? thank you
very much!

BRs
Gang Peng

  parent reply	other threads:[~2024-06-14  5:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  5:40 [Bug c++/115485] New: " gang.peng at aclsemi dot com
2024-06-14  5:51 ` [Bug c++/115485] " gang.peng at aclsemi dot com
2024-06-14  5:52 ` gang.peng at aclsemi dot com
2024-06-14  5:59 ` gang.peng at aclsemi dot com [this message]
2024-06-14 23:30 ` [Bug target/115485] " pinskia at gcc dot gnu.org
2024-06-15  2:00 ` gang.peng at aclsemi dot com
2024-06-15  3:21 ` pinskia at gcc dot gnu.org
2024-06-15  3:22 ` pinskia at gcc dot gnu.org
2024-06-15  6:30 ` gang.peng at aclsemi dot com
2024-06-20  8:56 ` gang.peng at aclsemi dot com
2024-06-23  0:37 ` pinskia at gcc dot gnu.org
2024-06-23  5:13 ` gang.peng at aclsemi dot com
2024-06-23  5:14 ` gang.peng at aclsemi dot com
2024-06-23 18:47 ` pinskia at gcc dot gnu.org
2024-06-23 23:59 ` [Bug target/115485] [11/12/13/14/15 Regression] " pinskia at gcc dot gnu.org
2024-06-24  0:09 ` pinskia at gcc dot gnu.org
2024-06-24 11:34 ` gang.peng at aclsemi dot com

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-115485-4-gEFekWY3aV@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).