https://gcc.gnu.org/g:f53c5cde64770d6c175737a444450fea81feba80

commit r15-9312-gf53c5cde64770d6c175737a444450fea81feba80
Author: Jakub Jelinek <ja...@redhat.com>
Date:   Tue Apr 8 12:39:16 2025 +0200

    riscv: Fix a typo in config/riscv/freebsd.h [PR119678]
    
    The r15-1124 commit had a typo in one of the FBSD_LINK_PG_NOTE
    macro uses.
    
    Fixed thusly, tested with
    ../configure --target riscv64-unknown-freebsd14 --disable-bootstrap 
--enable-languages=c --disable-libsanitizer --disable-libgomp
    make -j32
    Before it failed while compiling gcc.cc:
    In file included from ./tm.h:44,
                     from ../../gcc/gcc.cc:35:
    ../../gcc/config/riscv/freebsd.h:45:5: error: expected ‘,’ or ‘;’ before 
‘FBSD_LINK_PG_NOTES’
       45 |   " FBSD_LINK_PG_NOTES "                                            
    \
          |     ^~~~~~~~~~~~~~~~~~
    ../../gcc/gcc.cc:1211:32: note: in expansion of macro ‘LINK_SPEC’
    Now it fails later on during libgcc configury because I don't have
    corresponding binutils.
    
    2025-04-08  Jakub Jelinek  <ja...@redhat.com>
    
            PR target/119678
            * config/riscv/freebsd.h (LINK_SPEC): Use FBSD_LINK_PG_NOTE rather
            than non-existing FBSD_LINK_PG_NOTES.

Diff:
---
 gcc/config/riscv/freebsd.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/riscv/freebsd.h b/gcc/config/riscv/freebsd.h
index 2dc705532d83..217e0ac15e6f 100644
--- a/gcc/config/riscv/freebsd.h
+++ b/gcc/config/riscv/freebsd.h
@@ -42,7 +42,7 @@ along with GCC; see the file COPYING3.  If not see
 #define LINK_SPEC "                                            \
   -melf" XLEN_SPEC DEFAULT_ENDIAN_SPEC "riscv                  \
   %{p:%nconsider using `-pg' instead of `-p' with gprof (1)}   \
-  " FBSD_LINK_PG_NOTES "                                               \
+  " FBSD_LINK_PG_NOTE "                                                \
   %{v:-V}                                                      \
   %{assert*} %{R*} %{rpath*} %{defsym*}                                \
   -X                                                           \

Reply via email to