[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)

[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)

[sjames at gcc dot gnu.org]

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.

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[sjames at gcc dot gnu.org]

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

--- Comment #1 from Sam James <sjames at gcc dot gnu.org> ---
Created attachment 55373
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55373&action=edit
build.lo

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[pinskia at gcc dot gnu.org]

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
What is the host compiler?

It is the host compiler that is failing with -mcpu=native.

Can you add -v to the failing command in
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/build/build-aarch64-unknown-linux-gnu/libiberty
, e.g.

  aarch64-unknown-linux-gnu-gcc -c -DHAVE_CONFIG_H -pipe -mcpu=native
-fdiagnostics-color=always -ggdb3 -O2  -I.
-I/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/../include
 -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local
-pedantic  -D_GNU_SOURCE  -fPIC
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/hashtab.c
-o pic/hashtab.o -v

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[sjames at gcc dot gnu.org]

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

--- Comment #3 from Sam James <sjames at gcc dot gnu.org> ---
Host compiler is:
```
gcc (Gentoo 14.0.0 p, commit f9de5c24b9a6172d48786289035eed8f947c04c1) 14.0.0
20230616 (experimental) a371a639b76f1bdcd7a957f400b5a7c0faf30a15
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```

I'll try it with w/ GCC 13 in a minute.

```
#  aarch64-unknown-linux-gnu-gcc -c -DHAVE_CONFIG_H -pipe -mcpu=native
-fdiagnostics-color=always -ggdb3 -O2  -I.
-I/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/../include
 -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local
-pedantic  -D_GNU_SOURCE  -fPIC
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/hashtab.c
-o pic/hashtab.o -v
Using built-in specs.
COLLECT_GCC=aarch64-unknown-linux-gnu-gcc
Target: aarch64-unknown-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/configure
--host=aarch64-unknown-linux-gnu --build=aarch64-unknown-linux-gnu
--prefix=/usr --bindir=/usr/aarch64-unknown-linux-gnu/gcc-bin/14
--includedir=/usr/lib/gcc/aarch64-unknown-linux-gnu/14/include
--datadir=/usr/share/gcc-data/aarch64-unknown-linux-gnu/14
--mandir=/usr/share/gcc-data/aarch64-unknown-linux-gnu/14/man
--infodir=/usr/share/gcc-data/aarch64-unknown-linux-gnu/14/info
--with-gxx-include-dir=/usr/lib/gcc/aarch64-unknown-linux-gnu/14/include/g++-v14
--with-python-dir=/share/gcc-data/aarch64-unknown-linux-gnu/14/python
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --enable-nls --without-included-gettext
--disable-libunwind-exceptions --enable-checking=yes,extra,rtl
--with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 14.0.0 p,
commit f9de5c24b9a6172d48786289035eed8f947c04c1' --with-gcc-major-version-only
--enable-libstdcxx-time --enable-lto --disable-libstdcxx-pch --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--disable-multilib --disable-fixed-point --enable-libgomp --disable-libssp
--disable-libada --disable-cet --disable-systemtap
--disable-valgrind-annotations --disable-vtable-verify --disable-libvtv
--with-zstd --without-isl --enable-default-pie --enable-host-pie
--enable-default-ssp
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230616 (experimental)
a371a639b76f1bdcd7a957f400b5a7c0faf30a15 (Gentoo 14.0.0 p, commit
f9de5c24b9a6172d48786289035eed8f947c04c1)
COLLECT_GCC_OPTIONS='-fdiagnostics-color=always' '-c' '-D' 'HAVE_CONFIG_H'
'-pipe'  '-ggdb3' '-O2' '-I' '.' '-I'
'/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/../include'
'-Wextra' '-Wall' '-Wwrite-strings' '-Wc++-compat' '-Wstrict-prototypes'
'-Wshadow=local' '-Wpedantic' '-D' '_GNU_SOURCE' '-fPIC' '-o' 'pic/hashtab.o'
'-v' '-mlittle-endian' '-mabi=lp64'
'-mcpu=ares+crc+crypto+nofp+nolse+norcpc+nordma' '-dumpdir' 'pic/'
 /usr/libexec/gcc/aarch64-unknown-linux-gnu/14/cc1 -quiet -v -I . -I
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/../include
-dD -D HAVE_CONFIG_H -D _GNU_SOURCE
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/hashtab.c
-quiet -dumpdir pic/ -dumpbase hashtab.c -dumpbase-ext .c -mlittle-endian
-mabi=lp64 -mcpu=ares+crc+crypto+nofp+nolse+norcpc+nordma -ggdb3 -O2 -Wextra
-Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local
-Wpedantic -version -fdiagnostics-color=always -fPIC -o - |

/usr/lib/gcc/aarch64-unknown-linux-gnu/14/../../../../aarch64-unknown-linux-gnu/bin/as
-v -I . -I
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/../include
--gdwarf-5 -EL -march=armv8.2-a+crc+profile+nofp+nolse+nordma -mabi=lp64 -o
pic/hashtab.o
GNU assembler version 2.39.0 (aarch64-unknown-linux-gnu) using BFD version
(Gentoo 2.39 p6) 2.39.0
GNU C17 (Gentoo 14.0.0 p, commit f9de5c24b9a6172d48786289035eed8f947c04c1)
version 14.0.0 20230616 (experimental) a371a639b76f1bdcd7a957f400b5a7c0faf30a15
(aarch64-unknown-linux-gnu)
        compiled by GNU C version 14.0.0 20230616 (experimental)
a371a639b76f1bdcd7a957f400b5a7c0faf30a15, GMP version 6.2.99, MPFR version
4.2.0-p9, MPC version 1.3.1, isl version none
warning: GMP header version 6.2.99 differs from library version 6.2.1.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory
"/usr/lib/gcc/aarch64-unknown-linux-gnu/14/../../../../aarch64-unknown-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 .

/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/../include
 /usr/lib/gcc/aarch64-unknown-linux-gnu/14/include
 /usr/local/include
 /usr/lib/gcc/aarch64-unknown-linux-gnu/14/include-fixed
 /usr/include
End of search list.
Compiler executable checksum: b5ab029ba38daef01d5d7aa5d6bab700
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/hashtab.c:
In function ‘htab_collisions’:
/var/tmp/portage/sys-devel/gcc-14.0.0.9999/work/gcc-14.0.0.9999/libiberty/hashtab.c:798:1:
error: ‘+nofp’ feature modifier is incompatible with the use of floating-point
types
  798 | htab_collisions (htab_t htab)
      | ^~~~~~~~~~~~~~~
```

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |build

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
driver-aarch64.cc is either being miscompiled or has the wrong logic dealing
with fp or the linux kernel is no longer printing out fp feature in
/proc/cpuinfo .

So can you also cat /proc/cpuinfo ?

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[pinskia at gcc dot gnu.org]

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>-march=armv8.2-a+crc+profile+nofp+nolse+nordma

This seems totally wrong ....

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[sjames at gcc dot gnu.org]

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

--- Comment #6 from Sam James <sjames at gcc dot gnu.org> ---
Created attachment 55374
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55374&action=edit
/proc/cpuinfo

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[sjames at gcc dot gnu.org]

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

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #7 from Sam James <sjames at gcc dot gnu.org> ---
Ugh, I just realised I was using --personality=arm which is almost certainly it
(used bash history without checking). Sorry for the noise. I'll reopen if it
still happens but I doubt it will.

[Bug bootstrap/110325] [14 regression] Build failure on arm64 (libiberty/physmem.c:83:1: error: ‘+nofp’ feature modifier is incompatible with the use of floating-point types)

[pinskia at gcc dot gnu.org]

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

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Sam James from comment #7)
> Ugh, I just realised I was using --personality=arm which is almost certainly
> it (used bash history without checking). Sorry for the noise. I'll reopen if
> it still happens but I doubt it will.

Yes that will definitely change /proc/cpuinfo and you can see a reference to
vfp rather than fp and such.