public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/110325] New: [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)
Date: Tue, 20 Jun 2023 16:32:30 +0000	[thread overview]
Message-ID: <bug-110325-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110325
           Summary: [14 regression] Build failure on arm64
                    (libiberty/physmem.c:83:1: error: ‘+nofp’ feature
                    modifier is incompatible with the use of
                    floating-point types)
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sjames at gcc dot gnu.org
  Target Milestone: ---

I've been slacking with my ~daily tests, so this started in the last 2 weeks or
so. I suspect it's really more the last few days.

```
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/physmem.c:
In function ‘physmem_total’:
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/physmem.c:83:1:
error: ‘+nofp’ feature modifier is incompatible with the use of floating-point
types
   83 | physmem_total (void)
      | ^~~~~~~~~~~~~
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/physmem.c:
In function ‘physmem_available’:
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/physmem.c:187:1:
error: ‘+nofp’ feature modifier is incompatible with the use of floating-point
types
  187 | physmem_available (void)
      | ^~~~~~~~~~~~~~~~~
make[3]: *** [Makefile:1191: physmem.o] Error 1
```

This is at commit 0be3a051c03965c5c0385b783837154902bc08fa. Let me know what
more information is needed.

             reply	other threads:[~2023-06-20 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 16:32 sjames at gcc dot gnu.org [this message]
2023-06-20 16:33 ` [Bug bootstrap/110325] " sjames at gcc dot gnu.org
2023-06-20 16:39 ` pinskia at gcc dot gnu.org
2023-06-20 16:42 ` sjames at gcc dot gnu.org
2023-06-20 16:43 ` pinskia at gcc dot gnu.org
2023-06-20 16:44 ` pinskia at gcc dot gnu.org
2023-06-20 16:53 ` sjames at gcc dot gnu.org
2023-06-20 16:54 ` sjames at gcc dot gnu.org
2023-06-20 17:11 ` 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-110325-4@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).