public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Fiodar Stryzhniou <fedor_qd@mail.ru>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Warnings in GCC 12.1.0 builds
Date: Sun, 12 Jun 2022 16:06:21 +0300	[thread overview]
Message-ID: <df5fde71-4f5e-a92e-2c24-a2395fe4df57@mail.ru> (raw)

OS - Devuan Chimaera 4.0 stable release

Config:
configure  --target=$TARGET --prefix=$PREFIX  --without-headers \
      --enable-languages="c,c++,lto" --enable-lto --enable-interwork \
      --enable-long-long --enable-tls --enable-multilib --enable-wchar_t \
      --enable-c99 --with-newlib --with-dwarf2 
--with-static-standard-libraries \
      --disable-hosted-libstdcxx --disable-libstdcxx-pch --disable-shared \
      --disable-option-checking --disable-threads --disable-nls \
      --disable-win32-registry --disable-libssp --disable-libquadmath

I hope this helps. Listed warnings:

1)
Links are now set up to build a cross-compiler
  from x86_64-pc-linux-gnu to arm-none-symbianelf.
/d/gcc-12.1.0/gcc-12.1.0/gcc/gengtype-lex.l: In function ‘int 
yylex(const char**)’:
gengtype-lex.cc:356:15: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
/d/gcc-12.1.0/gcc-12.1.0/gcc/gengtype-lex.l:119:1: note: in expansion of 
macro ‘YY_DO_BEFORE_ACTION’
/d/gcc-12.1.0/gcc-12.1.0/gcc/gengtype-lex.l:114:1: note: here
gengtype-lex.cc:356:15: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
/d/gcc-12.1.0/gcc-12.1.0/gcc/gengtype-lex.l:139:1: note: in expansion of 
macro ‘YY_DO_BEFORE_ACTION’
/d/gcc-12.1.0/gcc-12.1.0/gcc/gengtype-lex.l:135:1: note: here

2)
In file included from ../../gcc-12.1.0/./gcc/coretypes.h:478,
                  from ../../gcc-12.1.0/./gcc/expmed.cc:26:
../../gcc-12.1.0/./gcc/machmode.h: In function ‘rtx_def* 
emit_store_flag_1(rtx, rtx_code, rtx, rtx, machine_mode, int, int, 
machine_mode)’:
../../gcc-12.1.0/./gcc/machmode.h:550:42: warning: ‘int_mode’ may be 
used uninitialized in this function [-Wmaybe-uninitialized]
   550 |    ? mode_size_inline (mode) : mode_size[mode]);
       |                                          ^~~~
../../gcc-12.1.0/./gcc/expmed.cc:5657:19: note: ‘int_mode’ was declared here
  5657 |   scalar_int_mode int_mode;

3)
In file included from ../../gcc-12.1.0/./gcc/splay-tree-utils.h:491,
                  from ../../gcc-12.1.0/./gcc/rtl-ssa.h:45,
                  from ../../gcc-12.1.0/./gcc/rtl-ssa/accesses.cc:28:
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc: In static member function 
‘static void base_splay_tree<Accessors>::print(pretty_printer*, typename 
Accessors::node_type, Printer, char, vec<char>&) [with Printer = 
rtl_ssa::set_info::print_uses_on_new_lines(pretty_printer*) 
const::<lambda(pretty_printer*, splay_tree_node<rtl_ssa::use_info*>*)>; 
Accessors = 
splay_tree_accessors_without_parent<default_splay_tree_accessors<splay_tree_node<rtl_ssa::use_info*>*> 
 >]’:
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:92:19: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
    92 |   extra_indent[1] = code;
       |   ~~~~~~~~~~~~~~~~^~~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:93:19: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
    93 |   extra_indent[2] = ']';
       |   ~~~~~~~~~~~~~~~~^~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:100:19: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   100 |   extra_indent[1] = (left || right ? '|' : ' ');
       |   ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:101:19: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   101 |   extra_indent[2] = ' ';
       |   ~~~~~~~~~~~~~~~~^~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:120:23: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   120 |       extra_indent[1] = '+';
       |       ~~~~~~~~~~~~~~~~^~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:121:23: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   121 |       extra_indent[2] = '-';
       |       ~~~~~~~~~~~~~~~~^~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:127:23: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   127 |       extra_indent[1] = right ? '|' : ' ';
       |       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:128:23: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   128 |       extra_indent[2] = ' ';
       |       ~~~~~~~~~~~~~~~~^~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:127:23: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   127 |       extra_indent[1] = right ? '|' : ' ';
       |       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
../../gcc-12.1.0/./gcc/splay-tree-utils.tcc:128:23: warning: writing 1 
byte into a region of size 0 [-Wstringop-overflow=]
   128 |       extra_indent[2] = ' ';

4)
../../../../gcc-12.1.0/./libgcc/config/arm/lib1funcs.S: Assembler messages:
../../../../gcc-12.1.0/./libgcc/config/arm/lib1funcs.S:2057: conditional 
infixes are deprecated in unified syntax

5)
../../../gcc-12.1.0/./libgcc/config/arm/pr-support.c: In function 
'_Unwind_GetDataRelBase':
../../../gcc-12.1.0/./libgcc/config/arm/pr-support.c:380:1: warning: 
control reaches end of non-void function [-Wreturn-type]
   380 | }
       | ^
../../../gcc-12.1.0/./libgcc/config/arm/pr-support.c: In function 
'_Unwind_GetTextRelBase':
../../../gcc-12.1.0/./libgcc/config/arm/pr-support.c:386:1: warning: 
control reaches end of non-void function [-Wreturn-type]
   386 | }

6)
../../../../gcc-12.1.0/./libgcc/config/arm/lib1funcs.S:1572:2: warning: 
#warning "No speculation barrier defined for this platform" [-Wcpp]

-- 
Fiodar Stryzhniou

                 reply	other threads:[~2022-06-12 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=df5fde71-4f5e-a92e-2c24-a2395fe4df57@mail.ru \
    --to=fedor_qd@mail.ru \
    --cc=gcc-help@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).