public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.spickett at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108642] ACLE function __arm_wsr missing for AArch64
Date: Thu, 02 Feb 2023 17:09:02 +0000	[thread overview]
Message-ID: <bug-108642-4-z7ycmhQAGx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108642-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from David Spickett <david.spickett at linaro dot org> ---
Of course, I was just looking at at assembly output in compiler explorer and
then locally I didn't link the object. That's why it seemed to work.

Compiling and linking I get:
$ ./bin/aarch64-none-linux-gnu-gcc /tmp/test.c -o /tmp/test.o
/tmp/test.c: In function ‘writeStatusWord’:
/tmp/test.c:4:39: warning: implicit declaration of function ‘__arm_wsr’
[-Wimplicit-function-declaration]
    4 | void writeStatusWord(uint32_t fpsr) { __arm_wsr("fpsr", fpsr); }
      |                                       ^~~~~~~~~
<...>aarch64-none-linux-gnu/bin/ld: /tmp/ccLie8Sh.o: in function
`writeStatusWord':
test.c:(.text+0x18): undefined reference to `__arm_wsr'
collect2: error: ld returned 1 exit status

Which makes more sense.

  parent reply	other threads:[~2023-02-02 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 16:57 [Bug c++/108642] New: ACLE function __arm_wsr missing when compiling in C++ mode " david.spickett at linaro dot org
2023-02-02 17:04 ` [Bug target/108642] ACLE function __arm_wsr missing " pinskia at gcc dot gnu.org
2023-02-02 17:06 ` pinskia at gcc dot gnu.org
2023-02-02 17:07 ` pinskia at gcc dot gnu.org
2023-02-02 17:09 ` david.spickett at linaro dot org [this message]
2023-02-02 17:10 ` pinskia at gcc dot gnu.org
2023-02-03 16:25 ` david.spickett at linaro dot 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-108642-4-z7ycmhQAGx@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).