public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/104749] [12/13 regression] stage1 d21 fails to link with GDC 9.1
Date: Wed, 07 Dec 2022 12:06:30 +0000 [thread overview]
Message-ID: <bug-104749-4-P29d9drK4s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104749-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104749
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[12/13 regression] stage1 |[12/13 regression] stage1
|d21 fails to link on |d21 fails to link with GDC
|Solaris/x86 |9.1
--- Comment #12 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Iain Buclaw from comment #6)
> Just having a look around, I couldn't see anywhere that `___s` would be
> created now.
>
> Then I came across r9-8460, which was fixed for 10.1.0, and backported
> before 9.4.0 was released. Linked bug report is pr d/94240.
>
> In that case then, earlier versions of version 9 might not work correctly.
I have, by the way, confirmed that cherry-picking commit
r9-8460-ge926d076f28a91f3ea30bd0bcfa1f25958fdb59e "d: Fix ICE in
add_symbol_to_partition_1, at lto/lto-partition.c:215" on top of GCC 9.1 does
resolve the issue discussed here (for x86_64-pc-linux-gnu).
... but for 'gcc/doc/install.texi' we'd rather state "GDC compiler (GCC version
9.4 or later)", I suppose.
next prev parent reply other threads:[~2022-12-07 12:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 19:13 [Bug d/104749] New: [12 regression] stage1 d21 fails to link on Solaris/x86 ro at gcc dot gnu.org
2022-03-01 19:18 ` [Bug d/104749] " ro at gcc dot gnu.org
2022-03-01 19:18 ` ro at gcc dot gnu.org
2022-03-01 19:18 ` ro at gcc dot gnu.org
2022-03-02 8:56 ` rguenth at gcc dot gnu.org
2022-03-02 9:39 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-03 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-03-03 12:35 ` ibuclaw at gdcproject dot org
2022-03-09 10:28 ` rguenth at gcc dot gnu.org
2022-05-06 8:32 ` [Bug d/104749] [12/13 " jakub at gcc dot gnu.org
2022-11-08 8:17 ` ro at gcc dot gnu.org
2022-11-10 10:24 ` tschwinge at gcc dot gnu.org
2022-12-07 12:06 ` tschwinge at gcc dot gnu.org [this message]
2022-12-20 13:37 ` [Bug d/104749] [12/13 regression] stage1 d21 fails to link with GDC 9.1 cvs-commit at gcc dot gnu.org
2022-12-20 13:37 ` cvs-commit at gcc dot gnu.org
2022-12-20 13:37 ` 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-104749-4-P29d9drK4s@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).