public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "herrtimson at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/102842] [10 Regression] ICE in cselib_record_set at -O2 or greater
Date: Thu, 21 Oct 2021 12:35:09 +0000 [thread overview]
Message-ID: <bug-102842-4-PGKMAXJ73x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102842-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102842
tt_1 <herrtimson at yahoo dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #11 from tt_1 <herrtimson at yahoo dot de> ---
(In reply to Martin Liška from comment #10)
> > Hint: its not an option to upgrade to gcc-11.2.0, since the cross compile
> > bootstrap is fundamentally broken by missing fenv header in the gcc-11
> > branch. Mixing up host and target compiler versions is nothing to desire,
> > its a place where there will be dragons.
>
> Oh, is it something we can help with? Is it a problem of the compiler?
the fenv bug is not new and was reported via #100017, there is already a
discussion with two possible solutions. The title is a bit misleading, I hit it
when I bootstrap a rootfs with all libs and headers for the armv7 target.
it seems that the fix for my gcc-10 bug was a stray commit without any bug
report, so I don't know who and where to ask for a proper backport. Gentoo's
gcc maintainer trofi (Sergey Trofimov) has resigned, to my great misfortune, so
I'm kind of lost with the process. Can we at least reopen? The bug is def not
fixed in the gcc-10 branch.
next prev parent reply other threads:[~2021-10-21 12:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 14:43 [Bug other/102842] New: [10 Regression] ICE in cselib_record_set at 02 " herrtimson at yahoo dot de
2021-10-19 14:43 ` [Bug other/102842] " herrtimson at yahoo dot de
2021-10-19 14:50 ` marxin at gcc dot gnu.org
2021-10-19 14:55 ` herrtimson at yahoo dot de
2021-10-19 18:36 ` [Bug rtl-optimization/102842] " pinskia at gcc dot gnu.org
2021-10-19 18:43 ` [Bug rtl-optimization/102842] [10/11/12 " pinskia at gcc dot gnu.org
2021-10-20 8:28 ` [Bug rtl-optimization/102842] [10 Regression] ICE in cselib_record_set at -O2 " marxin at gcc dot gnu.org
2021-10-20 10:46 ` marxin at gcc dot gnu.org
2021-10-20 10:46 ` marxin at gcc dot gnu.org
2021-10-20 11:32 ` herrtimson at yahoo dot de
2021-10-20 12:19 ` marxin at gcc dot gnu.org
2021-10-20 15:29 ` herrtimson at yahoo dot de
2021-10-21 7:25 ` marxin at gcc dot gnu.org
2021-10-21 12:35 ` herrtimson at yahoo dot de [this message]
2021-10-21 17:47 ` vmakarov at gcc dot gnu.org
2021-10-26 19:17 ` cvs-commit at gcc dot gnu.org
2021-10-30 10:32 ` [Bug rtl-optimization/102842] [10/11/12 " herrtimson at yahoo dot de
2021-11-03 17:47 ` cvs-commit at gcc dot gnu.org
2021-11-03 17:48 ` cvs-commit at gcc dot gnu.org
2021-11-05 13:51 ` 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-102842-4-PGKMAXJ73x@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).