X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net;
	s=badeba3b8450; t=1583957898;
	bh=rX31H7y7lAAIAZfvreCzaG4CDp1n9faJPXSKmdESmpw=;
	h=X-UI-Sender-Class:Date:From:To:CC:Subject:References:In-Reply-To;
	b=CRqiwfkM/MuFgFUEGM7BG42FHK3NpyakfxnJrDmqiBkh8cOiHce7SatHanCr0MdFg
	OvdYpyn7ZJgiz3VxM26GAHjUIn+Ha/6RtEsTu3f5G1C86gXOGk6fmmx4SNWQYtzJa4
	fUR65HDI1FMHR6t6sF0GzTodf2sC46iW94Uzmnzw=
X-UI-Sender-Class:	01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Message-ID:	<5E694788.5090308@gmx.de>
Date:	Wed, 11 Mar 2020 21:18:16 +0100
From:	"Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
User-Agent:	Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
CC:	stsp AT users DOT sourceforge DOT net
Subject:	Re: ANNOUNCE: DJGPP port of GNU binutils 2.34 uploaded.
References:	<202003101900 DOT 02AJ0s2L026948 AT delorie DOT com> <88b53f3e-5c10-256f-5a0c-aa942a48c6e9 AT gmail DOT com>
In-Reply-To:	<88b53f3e-5c10-256f-5a0c-aa942a48c6e9@gmail.com>
X-Provags-ID:	V03:K1:2aILgAvv22MtpLHLukJMGR2RqC4nQHHAAC8PMuQmKICC7dvFKgp
	W+vCHcQUTcLfHnvAVyP1SbJVnu8TTU03J6Vw6CnTnP6q6r2FyaA13w7EqJidbdAd/7VJk/m
	x7yS1R0FNjEKwM2KPKsxC6jZuajjTtOrbINSdsVnxOjeNoqm2PmFoDMghygiYSzZrChtCQ+
	R2vXvNkA39Kew4VGfYiOw==
X-Spam-Flag:	NO
X-UI-Out-Filterresults:	notjunk:1;V03:K0:hFL+YmVQR/E=:BoybYVKoQbgg/AWMrQsi5r
	d3+hSF507lfR9Us9JeepDc50lzr5Vgx+L+jvQXrNVT41JAvqcZAC+ZNEP0QkM4dD7uVRwPyzu
	KNG8NtYY6C07c+a+JYRt4s11X8vyL//tPjIUyx7fy4OtO4FCvDOAZ+9EV2KQ3o+CYVqaBUm1N
	hK9IbMdjeeBOWJjMeRyNzgg4o+NrqxB9wBYRp6eH6PlJotU0tiG/+g0JcZIEkORg/ZKNk5uge
	/SUYLMDBsXgBAhZfk9uZJbWl4hnZnyVDgSk9Gh13o7uMjJ/BGWUDdqWuMwoTY9anRsXJ1YGLL
	ypEQlHvqcgH76FMjvQhFpft7YeRxCMIi3MC/KNQZCYGuN/upc64ZV9OVdESIi8ZC54DSN8wiV
	KnVu8xHvohaYdMlT0b85e3MqRowLF1ABSRPy1mV0bBec6ITSIPIbbrwDl+kLwk7Bw6wX/0aYL
	FDXYgJtxaE/usYxTKwA9L2dgwwwGGdkM59Tra4pW3+78/GZYnKTV7tenPuwqRhRNwzWZKJQ09
	gseixx78R2+20PKpaZ+1ivolAI+X7QvzoiZeOtH+Em7fDeU5ADXqjvqOraKQULoUgDvddawEY
	CfYopc/9SoqCxLEo9MHruzvJeaWicwtkgfjSMTxIZB5364NwVQgkNhST9H8hKzDsfVv583V+7
	zI2VrpmFoqP2StROMMoLu5175CjHChiOHg4/6OAwdbYckaepb6+tBMz9/29dVeIbyrcFdRi1F
	W/CiyFZAdU/GBYE/Lq/Zj2NUcFgXgHywejI7LTR4VddGtF72x4xYMP6jyrXVtReP+SjB6DVeo
	13M316Bls6JSkSx2ImWTg9KSzxhrI/ihEeTXG2a4LDzFTSs1k4bTI2M5Vs78/a//uLhibAiT+
	VNSaESWWyoXAgYXZLP0lVh0IwhSjQdJCVcwTZAIb/wQ8QOKWJihHR3ZfkUX7BXlcY/4a0gMBW
	ALg6ZpTQ/3TADnCkaxiTYEqCbZeo0kEdKZN04N/93PTKumGvpBt3hVJBemrN+HG5qFP8xn++f
	om8LTgDHThGIfF2wjUqonKCaJmPhnrgWDpcnW1BV1KCXtJ504AFIiIx76ZSWSpRs9iXtpPohG
	smIKLFEGpmW5oooQUDJ03/W1P7lsOvkHlPX9dM6UH2iktKI/w8RnsEbc/A0w3Eg4b+sfMYuNz
	3kdu5u4mO9DOlCb8eF92JbQMeEnGnCuvvtF6g+fkkjU+13l9/OdzGernKVyzy0RPpyMJd+26V
	FvAQgftUOxLSmRlmS
Reply-To:	djgpp AT delorie DOT com

Am 11.03.2020 15:56, schrieb J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]:

[snip]
>>    DJGPP specific changes.
>>    =======================
>>    - There are no DJGPP specific changes compared with the previous port.
>>      The DJGPP specific changes enumerated below are the same than the ones
>>      already available in the previous port.
>
> Are there any plans to have these changes (even partially) upstreamed
> to GNU?  Because currently the upstream version is unusable even for
> cross-compiling, primarily due to a missing '_environ' symbol in the
> ldscripts.

No, I have no intention to upstream the patch to GNU.  Primary due to my
limited english skills I do not want to become involved in endless discussions
about a port that may be considered today as archaic by the maintainers.
I do not even know if there is still an official COFF and/or djgpp maintainer
of binutils.
Neitherless everybody is invited to review the patch and to try to get part
of it upstreamed into binutils.  I will not interfer nor make any claims on
it.  If you think you can convince the binutils maintainers to accept parts
of the patch that make the cross-compiler work again or if you have a better
solution for the djgpp specific issues, please feel free to go ahaed.
If there are any other parts of the patch that you think are usefull to get
included into binutils again, go ahead.


>>    - The linker script has been adapted to discard LTO sections created by the
>>      compiler if the -flto flag is passed to the compiler.
>
> This line has no effect though.  It reads:
>
>      /DISCARD/ : { *(gnu.lto_*) }
>
> but should be:
>
>      /DISCARD/ : { *(.gnu.lto_*) }
>
> with a leading dot in the section name.  Same issue with the dxe.ld and
> djgpp.djl scripts in cvs.  Especially for DXE it can be a problem
> because dxegen expects only one section in the input file.
>
>>      This is due to LTO
>>      specific file names that are not 8.3 clean especially if the -save-temps
>>      option is used.  This may change in the future when the djgpp port of the
>>      compiler fully supports LTO.
>
> I thought it was only because LTO information is useless in
> executables?  It's only needed during linking, and becomes just bloat
> after that.

IIRC, the LTO stuff was provided and/or suggested by Andris Pavenis some time
ago when he created one of the gcc ports.  Either I missed the missing leading
dot in the scripts or the provided patch was broken.  Anyway, I will fix this in
the differnt scripts ASAP.

Regards,
Juan M. Guerrero

- Raw text -