public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110652] New: [14 Regression] bootstrap failure on tree-vect-stmts.cc with  --enable-checking=release: error: 'new_temp' may be used uninitialized
Date: Thu, 13 Jul 2023 09:23:20 +0000	[thread overview]
Message-ID: <bug-110652-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110652
           Summary: [14 Regression] bootstrap failure on
                    tree-vect-stmts.cc with  --enable-checking=release:
                    error: 'new_temp' may be used uninitialized
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: slyfox at gcc dot gnu.org
  Target Milestone: ---

Noticed build failure today when built r14-2495-g43ed05a08963a5 as:

$ ~/dev/git/gcc/configure --disable-multilib --enable-checking=release
$ make
...
/tmp/gb/./prev-gcc/xg++ -B/tmp/gb/./prev-gcc/
-B/usr/local/x86_64-pc-linux-gnu/bin/ -nostdinc++
-B/tmp/gb/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/tmp/gb/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs 
-I/tmp/gb/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu 
-I/tmp/gb/prev-x86_64-pc-linux-gnu/libstdc++-v3/include 
-I/home/slyfox/dev/git/gcc/libstdc++-v3/libsupc++
-L/tmp/gb/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tmp/gb/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs  -fno-PIE -c  
-g -O2 -fno-checking -gtoggle -DIN_GCC    -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Wconditionally-supported
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Werror   -DHAVE_CONFIG_H -fno-PIE -I. -I.
-I/home/slyfox/dev/git/gcc/gcc -I/home/slyfox/dev/git/gcc/gcc/.
-I/home/slyfox/dev/git/gcc/gcc/../include 
-I/home/slyfox/dev/git/gcc/gcc/../libcpp/include
-I/home/slyfox/dev/git/gcc/gcc/../libcody 
-I/home/slyfox/dev/git/gcc/gcc/../libdecnumber
-I/home/slyfox/dev/git/gcc/gcc/../libdecnumber/bid -I../libdecnumber
-I/home/slyfox/dev/git/gcc/gcc/../libbacktrace   -o tree-vect-stmts.o -MT
tree-vect-stmts.o -MMD -MP -MF ./.deps/tree-vect-stmts.TPo
/home/slyfox/dev/git/gcc/gcc/tree-vect-stmts.cc
In file included from /home/slyfox/dev/git/gcc/gcc/hash-table.h:248,
                 from /home/slyfox/dev/git/gcc/gcc/coretypes.h:486,
                 from /home/slyfox/dev/git/gcc/gcc/tree-vect-stmts.cc:24:
In member function 'T* vec<T, A, vl_embed>::quick_push(const T&) [with T =
tree_node*; A = va_heap]',
    inlined from 'T* vec<T>::quick_push(const T&) [with T = tree_node*]' at
/home/slyfox/dev/git/gcc/gcc/vec.h:1987:28,
    inlined from 'bool vectorizable_load(vec_info*, stmt_vec_info,
gimple_stmt_iterator*, gimple**, slp_tree, stmt_vector_for_cost*)' at
/home/slyfox/dev/git/gcc/gcc/tree-vect-stmts.cc:10962:23:
/home/slyfox/dev/git/gcc/gcc/vec.h:1023:9: error: 'new_temp' may be used
uninitialized [-Werror=maybe-uninitialized]
 1023 |   *slot = obj;
      |   ~~~~~~^~~~~

$ /tmp/gb/./prev-gcc/xg++ -B/tmp/gb/./prev-gcc/ -v
Reading specs from /tmp/gb/./prev-gcc/specs
COLLECT_GCC=/tmp/gb/./prev-gcc/xg++
COLLECT_LTO_WRAPPER=/tmp/gb/./prev-gcc/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /home/slyfox/dev/git/gcc/configure --disable-multilib
--enable-checking=release
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230713 (experimental) (GCC)

             reply	other threads:[~2023-07-13  9:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  9:23 slyfox at gcc dot gnu.org [this message]
2023-07-13 15:12 ` [Bug tree-optimization/110652] " pinskia at gcc dot gnu.org
2023-07-13 15:15 ` pinskia at gcc dot gnu.org
2023-07-13 18:53 ` slyfox at gcc dot gnu.org
2023-07-14  1:04 ` linkw at gcc dot gnu.org
2023-07-14  2:55 ` linkw at gcc dot gnu.org
2023-07-14  6:04 ` linkw at gcc dot gnu.org
2023-07-14  8:27 ` rguenther at suse dot de
2023-07-15  0:34 ` pinskia at gcc dot gnu.org
2023-07-17  8:45 ` cvs-commit at gcc dot gnu.org
2023-07-17  8:46 ` linkw at gcc dot gnu.org
2023-07-17 10:33 ` slyfox 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-110652-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).