public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/99920] [10 regression] ICE building gcc 10 on power 7 BE
Date: Thu, 08 Apr 2021 08:55:15 +0000	[thread overview]
Message-ID: <bug-99920-4-l6mgAMv3YT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99920-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
So I can confirm the issue trying to build gcc10 packages for SLE11 ppc64
(after much massaging).  It works fine (past the failure point) on x86_64
with the same versioned host compiler.  It works fine when using gcc 4.8
as host compiler (also available on SLES11).

With the 4.3 based host compiler I see loads of

[  309s] In file included from ../../gcc/gimple-ssa-store-merging.c:168:
[  309s] ../../gcc/rtl.h: In function 'rtx_def* rtx_init(rtx_def*, rtx_code)':
[  309s] ../../gcc/rtl.h:2966: warning: invalid access to non-static data
member 'rtx_def::u' of NULL object
[  309s] ../../gcc/rtl.h:2966: warning: (perhaps the 'offsetof' macro was used
incorrectly)

also

[  625s] ../../gcc/cp/parser.c:31339:   instantiated from here
[  625s] ../../gcc/vec.h:1285: warning: invalid access to non-static data
member
 'vec<class_decl_loc_t::class_key_loc_t, va_heap, vl_embed>::m_vecdata' of NULL 
object
[  625s] ../../gcc/vec.h:1285: warning: (perhaps the 'offsetof' macro was used
incorrectly)
[  625s] ../../gcc/vec.h: In static member function 'static size_t vec<T, A,
vl_embed>::embedded_size(unsigned int) [with T = cp_expr, A = va_heap]':


when I bootstrap with STAGE1_CFLAGS="-O2 -g" then it gets past the failure
point as well (this does hint at some C++ initialization issue, IIRC those
plagued us a lot).  Note we're using STAGE1_CFLAGS="-O2 -g" for our
package builds (because we use known-good host compilers and to speed up
builds...) so we wouldn't have noticed this issue.

I'm still confident the error lies with our patched GCC 4.3.3 but I'm not
too interested in tracking the issue down ...

  parent reply	other threads:[~2021-04-08  8:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 22:28 [Bug bootstrap/99920] New: " seurer at gcc dot gnu.org
2021-04-06  7:29 ` [Bug bootstrap/99920] " rguenth at gcc dot gnu.org
2021-04-06  7:31 ` jakub at gcc dot gnu.org
2021-04-06  9:24 ` jakub at gcc dot gnu.org
2021-04-06 13:02 ` seurer at gcc dot gnu.org
2021-04-06 13:09 ` rguenther at suse dot de
2021-04-06 13:30 ` jakub at gcc dot gnu.org
2021-04-06 16:04 ` jakub at gcc dot gnu.org
2021-04-06 17:11 ` seurer at gcc dot gnu.org
2021-04-06 17:40 ` seurer at gcc dot gnu.org
2021-04-07  8:13 ` jakub at gcc dot gnu.org
2021-04-07  8:26 ` rguenther at suse dot de
2021-04-07 17:57 ` seurer at gcc dot gnu.org
2021-04-07 18:56 ` jakub at gcc dot gnu.org
2021-04-08  8:55 ` rguenth at gcc dot gnu.org [this message]
2021-04-08 10:53 ` rguenth at gcc dot gnu.org
2021-04-08 11:19 ` rguenth at gcc dot gnu.org
2021-04-08 11:52 ` rguenth at gcc dot gnu.org
2021-04-08 11:53 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-08 14:15 ` seurer at gcc dot gnu.org
2022-01-11 11:10 ` [Bug bootstrap/99920] [10 regression] ICE building gcc 10 on power 7 BE with GCC 4.3.4 (SUSE) host compiler 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-99920-4-l6mgAMv3YT@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).