From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Iain Buclaw via Gcc-patches <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH] d: Fix #error You must define PREFERRED_DEBUGGING_TYPE if DWARF is not supported (PR105659)
Date: Wed, 07 Sep 2022 15:11:17 +0200 [thread overview]
Message-ID: <1662554645.snslqua0b8.astroid@pulse.none> (raw)
In-Reply-To: <ydd5yhzxsqr.fsf@CeBiTec.Uni-Bielefeld.DE>
Excerpts from Rainer Orth's message of September 7, 2022 2:40 pm:
> Hi Iain,
>
>>> Yes, this is data related. The DSO registry picks up nothing in the
>>> miscompiled stage2 compiler, leaving all data uninitialized. The stage1
>>> compiler works, and runs all module constructors ahead of compilation.
>>>
>>
>> Ohh, backtrack on that, analysis is correct, but it is a compiler regression.
>>
>> The TARGET_D_MINFO_SECTION macros are in elfos.h, which of course no
>> longer get pulled in to sol2-d.cc after I removed the tm.h include.
>>
>> Re-adding these two ought to fix the bootstrap for you.
>>
>> #include "tm.h"
>> #include "memmodel.h"
>
> it does indeed: with that patch, i386-pc-solaris2.11 and
> sparc-sun-solaris2.11 bootstraps completed successfully and test results
> are back to normal.
>
> Thanks a lot.
>
I'm just running through various target configurations with memmodel.h
removed, I know it was used to be required for one of the targets
(probably SPARC), though that may have been because of the previously
included tm_p.h header.
Will have a think about a likely follow-up though.
Firstly fixing the outstanding issues with
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598078.html
Secondly possibly using a different method to coax out the object format
to the D target hooks, or front-end.
Iain.
next prev parent reply other threads:[~2022-09-07 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 21:16 Iain Buclaw
2022-08-26 8:42 ` Richard Biener
2022-08-30 21:53 ` Joseph Myers
2022-08-31 12:10 ` Iain Buclaw
2022-08-31 17:16 ` Joseph Myers
2022-08-31 19:21 ` Iain Buclaw
2022-09-01 6:28 ` Richard Biener
2022-09-02 16:05 ` Iain Buclaw
2022-09-06 7:42 ` Rainer Orth
2022-09-06 10:51 ` Iain Buclaw
2022-09-06 12:04 ` Rainer Orth
2022-09-06 14:19 ` Iain Buclaw
2022-09-06 14:25 ` Rainer Orth
2022-09-06 17:02 ` Iain Buclaw
2022-09-06 21:41 ` Iain Buclaw
2022-09-07 7:34 ` Iain Buclaw
2022-09-07 12:40 ` Rainer Orth
2022-09-07 13:11 ` Iain Buclaw [this message]
2022-09-07 13:21 ` Rainer Orth
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=1662554645.snslqua0b8.astroid@pulse.none \
--to=ibuclaw@gdcproject.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).