public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/103309] [12 Regression] Random gcc/system.h:784:34: error: section type conflict
Date: Wed, 17 Nov 2021 21:15:46 +0000	[thread overview]
Message-ID: <bug-103309-4-HXmANfqgkV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103309-4@http.gcc.gnu.org/bugzilla/>

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);
      |   ^~~~~~~~~~

  reply	other threads:[~2021-11-17 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 20:59 [Bug bootstrap/103309] New: " hjl.tools at gmail dot com
2021-11-17 21:15 ` hjl.tools at gmail dot com [this message]
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

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-103309-4-HXmANfqgkV@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).