Greetings.
Could anybody tell me is this optimization bug on ARM was finally fixed...
* in gcc-4.9 as released with jessie?
* in gcc-6 as the default compiler in stretch?
I ask because I added this workaround to unzip's debian/rules:
ifeq ($(DEB_HOST_ARCH),armhf)
CFLAGS := DEB_CFLAGS_STRIP=-O
peter green wrote:
Matthias Klose wrote:
there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...).
Disabling stack protector also seems to result in a succesful compile
(reducing it from strong to regular does not).
And another workaround is to use -marm.
--
T
Matthias Klose wrote:
there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...).
Disabling stack protector also seems to result in a succesful compile
(reducing it from strong to regular does not).
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
w
Control: tags -1 + help
this is not seen on the gcc-4.9 Linaro branch, so a ARM porter should identify
the relevant backport.
On 12/25/2014 06:12 AM, Matthias Klose wrote:
> the escalation is wrong. there exist several workarounds for it (lowering the
> optimization, using gcc-4.8, ...). I asked
the escalation is wrong. there exist several workarounds for it (lowering the
optimization, using gcc-4.8, ...). I asked the ARM porters to address this
properly (Hector on IRC agreed to forward this), however I don't see any
progress here. Now CCing debian-arm explicitly.
On 12/23/2014 11:48 AM,
5 matches
Mail list logo
