public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict
@ 2021-11-17 20:59 hjl.tools at gmail dot com
  2021-11-17 21:15 ` [Bug bootstrap/103309] " hjl.tools at gmail dot com
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: hjl.tools at gmail dot com @ 2021-11-17 20:59 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 103309
           Summary: [12 Regression] Random gcc/system.h:784:34: error:
                    section type conflict
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
  Target Milestone: ---

On Linux/x86-64, I started getting:

/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/./prev-gcc/xg++
-B/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/./prev-gcc/
-B/usr/gcc-12.0.0-x86-64/x86_64-pc-linux-gnu/bin/ -nostdinc++
-B/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs

-I/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu

-I/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/prev-x86_64-pc-linux-gnu/libstdc++-v3/include
 -I/export/gnu/import/git/gitlab/x86-gcc/libstdc++-v3/libsupc++
-L/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/export/build/gnu/tools-build/gcc-gitlab/build-x86_64-linux/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
 -fno-PIE -c   -g -O2 -fchecking=1 -DIN_GCC     -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -Werror -fno-common  -DHAVE_CONFIG_H -I. -I.
-I/export/gnu/import/git/gitlab/x86-gcc/gcc
-I/export/gnu/import/git/gitlab/x86-gcc/gcc/.
-I/export/gnu/import/git/gitlab/x86-gcc/gcc/../include
-I/export/gnu/import/git/gitlab/x86-gcc/gcc/../libcpp/include
-I/export/gnu/import/git/gitlab/x86-gcc/gcc/../libcody 
-I/export/gnu/import/git/gitlab/x86-gcc/gcc/../libdecnumber
-I/export/gnu/import/git/gitlab/x86-gcc/gcc/../libdecnumber/bid
-I../libdecnumber -I/export/gnu/import/git/gitlab/x86-gcc/gcc/../libbacktrace  
-o passes.o -MT passes.o -MMD -MP -MF ./.deps/passes.TPo
/export/gnu/import/git/gitlab/x86-gcc/gcc/passes.c
In file included from /export/gnu/import/git/gitlab/x86-gcc/gcc/passes.c:26:
In member function ??hash_table<Descriptor, Lazy, Allocator>::value_type*
hash_table<Descriptor, Lazy, Allocator>::alloc_entries(size_t) const [with
Descriptor = hash_map<nofree_string_hash, opt_pass*>::hash_entry; bool Lazy =
false; Allocator = xcallocator]??,
    inlined from ??void hash_table<Descriptor, Lazy, Allocator>::expand() [with
Descriptor = hash_map<nofree_string_hash, opt_pass*>::hash_entry; bool Lazy =
false; Allocator = xcallocator]?? at
/export/gnu/import/git/gitlab/x86-gcc/gcc/hash-table.h:802:40:
/export/gnu/import/git/gitlab/x86-gcc/gcc/system.h:784:34: error: section type
conflict with ??void hash_table<Descriptor, Lazy, Allocator>::expand() [with
Descriptor = hash_map<nofree_string_hash, opt_pass*>::hash_entry; bool Lazy =
false; Allocator = xcallocator]??
  784 |    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0
: 0))
      |                      ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/export/gnu/import/git/gitlab/x86-gcc/gcc/hash-table.h:715:3: note: in
expansion of macro ??gcc_assert??
  715 |   gcc_assert (nentries != NULL);
      |   ^~~~~~~~~~
In file included from
/export/gnu/import/git/gitlab/x86-gcc/gcc/coretypes.h:482,
                 from /export/gnu/import/git/gitlab/x86-gcc/gcc/passes.c:27:
/export/gnu/import/git/gitlab/x86-gcc/gcc/hash-table.h: In member function
??void hash_table<Descriptor, Lazy, Allocator>::expand() [with Descriptor =
hash_map<nofree_string_hash, opt_pass*>::hash_entry; bool Lazy = false;
Allocator = xcallocator]??:
/export/gnu/import/git/gitlab/x86-gcc/gcc/hash-table.h:779:1: note: ??void
hash_table<Descriptor, Lazy, Allocator>::expand() [with Descriptor =
hash_map<nofree_string_hash, opt_pass*>::hash_entry; bool Lazy = false;
Allocator = xcallocator]?? was declared here
  779 | hash_table<Descriptor, Lazy, Allocator>::expand ()
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/export/gnu/import/git/gitlab/x86-gcc/gcc/coretypes.h:474,
                 from /export/gnu/import/git/gitlab/x86-gcc/gcc/expmed.c:26:
In function ??poly_uint16 mode_to_bytes(machine_mode)??,
    inlined from ??typename if_nonpoly<typename T::measurement_type>::type
GET_MODE_SIZE(const T&) [with T = scalar_int_mode]?? at
/export/gnu/import/git/gitlab/x86-gcc/gcc/machmode.h:647:24,
    inlined from ??rtx_def* emit_store_flag_1(rtx, rtx_code, rtx, rtx,
machine_mode, int, int, machine_mode)?? at
/export/gnu/import/git/gitlab/x86-gcc/gcc/expmed.c:5724:56:
/export/gnu/import/git/gitlab/x86-gcc/gcc/machmode.h:550:49: warning:
??*(unsigned int*)((char*)&int_mode + offsetof(scalar_int_mode,
scalar_int_mode::m_mode))?? may be used uninitialized in this function
[-Wmaybe-uninitialized]
  550 |           ? mode_size_inline (mode) : mode_size[mode]);
      |                                                 ^~~~
/export/gnu/import/git/gitlab/x86-gcc/gcc/expmed.c: In function ??rtx_def*
emit_store_flag_1(rtx, rtx_code, rtx, rtx, machine_mode, int, int,
machine_mode)??:
/export/gnu/import/git/gitlab/x86-gcc/gcc/expmed.c:5653:19: note: ??*(unsigned
int*)((char*)&int_mode + offsetof(scalar_int_mode, scalar_int_mode::m_mode))??
was declared here
 5653 |   scalar_int_mode int_mode;
      |                   ^~~~~~~~
make[5]: *** [Makefile:1138: passes.o] Error 1

It happened at random and is not reproducible by hand.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug bootstrap/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
@ 2021-11-17 21:15 ` hjl.tools at gmail dot com
  2021-11-17 23:04 ` [Bug middle-end/103309] " pinskia at gcc dot gnu.org
                   ` (5 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: hjl.tools at gmail dot com @ 2021-11-17 21:15 UTC (permalink / raw)
  To: gcc-bugs

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-11-17

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
The build error can happen on different source files.  But it always points
to

https://gcc.gnu.org/pipermail/gcc-regression/2021-November/075734.html

In member function ‘hash_table<Descriptor, Lazy, Allocator>::value_type*
hash_table<Descriptor, Lazy, Allocator>::alloc_entries(size_t) const [with
Descriptor = hash_map<tree_node*, auto_vec<gimple*> >::hash_entry; bool Lazy =
false; Allocator = xcallocator]’,
    inlined from ‘void hash_table<Descriptor, Lazy, Allocator>::expand() [with
Descriptor = hash_map<tree_node*, auto_vec<gimple*> >::hash_entry; bool Lazy =
false; Allocator = xcallocator]’ at ../../src-master/gcc/hash-table.h:802:40:
../../src-master/gcc/system.h:784:34: error: section type conflict with ‘void
hash_table<Descriptor, Lazy, Allocator>::expand() [with Descriptor =
hash_map<tree_node*, auto_vec<gimple*> >::hash_entry; bool Lazy = false;
Allocator = xcallocator]’
  784 |    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0
: 0))
      |                      ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../src-master/gcc/hash-table.h:715:3: note: in expansion of macro
‘gcc_assert’
  715 |   gcc_assert (nentries != NULL);
      |   ^~~~~~~~~~

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug middle-end/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
  2021-11-17 21:15 ` [Bug bootstrap/103309] " hjl.tools at gmail dot com
@ 2021-11-17 23:04 ` pinskia at gcc dot gnu.org
  2021-11-17 23:12 ` hjl.tools at gmail dot com
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-11-17 23:04 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
          Component|bootstrap                   |middle-end
             Target|                            |x86_64-linux

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Hmm, since this is stage2, that might mean stage 1 is being miscompiled.

What GCC/binutils version are you starting with?
Do you know when it started to fail like this?

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug middle-end/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
  2021-11-17 21:15 ` [Bug bootstrap/103309] " hjl.tools at gmail dot com
  2021-11-17 23:04 ` [Bug middle-end/103309] " pinskia at gcc dot gnu.org
@ 2021-11-17 23:12 ` hjl.tools at gmail dot com
  2021-11-17 23:14 ` pinskia at gcc dot gnu.org
                   ` (3 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: hjl.tools at gmail dot com @ 2021-11-17 23:12 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
I first ran into it with r12-5074.  I am using GCC 11.2.1 from Fedora 35
and binutils master branch.   For r12-5074, the only change on the machine
is the GCC source.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug middle-end/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
                   ` (2 preceding siblings ...)
  2021-11-17 23:12 ` hjl.tools at gmail dot com
@ 2021-11-17 23:14 ` pinskia at gcc dot gnu.org
  2021-11-17 23:28 ` hjl.tools at gmail dot com
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-11-17 23:14 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #3)
> I first ran into it with r12-5074.  I am using GCC 11.2.1 from Fedora 35
> and binutils master branch.   For r12-5074, the only change on the machine
> is the GCC source.

r12-5074 does not even touch anything used for x86_64 builds either ...

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug middle-end/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
                   ` (3 preceding siblings ...)
  2021-11-17 23:14 ` pinskia at gcc dot gnu.org
@ 2021-11-17 23:28 ` hjl.tools at gmail dot com
  2021-11-18  7:54 ` rguenth at gcc dot gnu.org
  2022-03-09 14:12 ` rguenth at gcc dot gnu.org
  6 siblings, 0 replies; 8+ messages in thread
From: hjl.tools at gmail dot com @ 2021-11-17 23:28 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andrew Pinski from comment #4)
> (In reply to H.J. Lu from comment #3)
> > I first ran into it with r12-5074.  I am using GCC 11.2.1 from Fedora 35
> > and binutils master branch.   For r12-5074, the only change on the machine
> > is the GCC source.
> 
> r12-5074 does not even touch anything used for x86_64 builds either ...

My tester doesn't check every commit.  This failure comes and goes at
random.  I have no idea when it was introduced.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug middle-end/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
                   ` (4 preceding siblings ...)
  2021-11-17 23:28 ` hjl.tools at gmail dot com
@ 2021-11-18  7:54 ` rguenth at gcc dot gnu.org
  2022-03-09 14:12 ` rguenth at gcc dot gnu.org
  6 siblings, 0 replies; 8+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-11-18  7:54 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |12.0

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug middle-end/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
  2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
                   ` (5 preceding siblings ...)
  2021-11-18  7:54 ` rguenth at gcc dot gnu.org
@ 2022-03-09 14:12 ` rguenth at gcc dot gnu.org
  6 siblings, 0 replies; 8+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-03-09 14:12 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Assuming fixed.

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2022-03-09 14:12 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-17 20:59 [Bug bootstrap/103309] New: [12 Regression] Random gcc/system.h:784:34: error: section type conflict hjl.tools at gmail dot com
2021-11-17 21:15 ` [Bug bootstrap/103309] " hjl.tools at gmail dot com
2021-11-17 23:04 ` [Bug middle-end/103309] " pinskia at gcc dot gnu.org
2021-11-17 23:12 ` hjl.tools at gmail dot com
2021-11-17 23:14 ` pinskia at gcc dot gnu.org
2021-11-17 23:28 ` hjl.tools at gmail dot com
2021-11-18  7:54 ` rguenth at gcc dot gnu.org
2022-03-09 14:12 ` rguenth at gcc dot gnu.org

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