public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107581] ICE on sparc-leon-uclibc during go build
Date: Wed, 09 Nov 2022 07:51:15 +0000	[thread overview]
Message-ID: <bug-107581-4-XRJ9OVlEtD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107581-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Marc Poulhiès <dkm at gcc dot gnu.org> ---
(In reply to Ian Lance Taylor from comment #1)
> This crash appears to be fairly deep in the middle-end.  Nothing has changed
> recently in the Go frontend.  Has this crash just started appearing, or is
> this the first time you are trying this?  If it is a relatively new crash
> then I think it must be related to some middle-end change.  Thanks.

This is a first try. I was trying 12.2.0 (ICE) then checked with trunk to see
if it was still crashing.


(In reply to Richard Biener from comment #2)
> I assume that reproducing with trunk is with checking enabled?  It would be
> nice if you can do a debugging session on the crashing go1 invocation and
> inspect the GIMPLE that's being expanded.  From the backtrace it looks like
> it's some

I don't think the build has any checking enabled but I have to check (that's
from a crosstool-ng build, so I doubt they are enabling checks).

I'll do a debug build and add the more detailed log here.

Thanks

  parent reply	other threads:[~2022-11-09  7:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 20:08 [Bug go/107581] New: " dkm at gcc dot gnu.org
2022-11-08 20:31 ` [Bug target/107581] " ian at airs dot com
2022-11-09  7:26 ` rguenth at gcc dot gnu.org
2022-11-09  7:51 ` dkm at gcc dot gnu.org [this message]
2022-11-09  8:46 ` dkm at gcc dot gnu.org
2022-11-09 16:11 ` dkm at gcc dot gnu.org
2022-11-09 16:12 ` dkm at gcc dot gnu.org
2022-11-09 22:59 ` ian at airs dot com
2022-11-10  0:09 ` cvs-commit at gcc dot gnu.org
2022-11-10  0:15 ` ian at airs dot com
2022-11-10  9:18 ` dkm at gcc dot gnu.org
2022-11-28 22:18 ` pinskia 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-107581-4-XRJ9OVlEtD@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).