[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#813784: marked as done (g++ fails to compile asymptote 2.35-4 correctly on MIPS with -O1 or higher optimisation)

Your message dated Thu, 20 Oct 2016 17:46:22 +0200
with message-id <20161020154622.oxzjlukb5jxuy6me@aurel32.net>
and subject line Re: g++ fails to compile asymptote 2.35-4 correctly on MIPS with -O1 or higher optimisation
has caused the Debian Bug report #813784,
regarding g++ fails to compile asymptote 2.35-4 correctly on MIPS with -O1 or higher optimisation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
813784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813784
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: g++-5
Version: 5.3.1-7
Severity: normal

In an attempt to track down the reason for bug#808821, I had an
extended discussion with the asymptote upstream, see
https://sourceforge.net/p/asymptote/bugs/205/
I came to the conclusion (using minkus) that the compilation works
with -O0 optimisation but not with -O1 optimisation, for some strange
reason that we couldn't fathom.  (I controlled the optimisation by
modifying the Makefile CFLAGS setting after running configure.)

I don't know how to construct a minimal case or how to further
investigate this beyond what I have already described in that bug
report, unfortunately.  It pretty much builds fine on all of the other
architectures; at least none of them exhibit the same error.

   Julian

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages g++-5 depends on:
ii  gcc-5            5.3.1-7
ii  gcc-5-base       5.3.1-7
ii  libc6            2.21-7
ii  libgmp10         2:6.1.0+dfsg-2
ii  libisl15         0.16.1-1
ii  libmpc3          1.0.3-1
ii  libmpfr4         3.1.3-2
ii  libstdc++-5-dev  5.3.1-7
ii  zlib1g           1:1.2.8.dfsg-2+b1

g++-5 recommends no packages.

Versions of packages g++-5 suggests:
pn  g++-5-multilib    <none>
pn  gcc-5-doc         <none>
pn  libstdc++6-5-dbg  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 5.4.1-2

On 2016-02-05 09:24, Julian Gilbey wrote:
> Package: g++-5
> Version: 5.3.1-7
> Severity: normal
> 
> In an attempt to track down the reason for bug#808821, I had an
> extended discussion with the asymptote upstream, see
> https://sourceforge.net/p/asymptote/bugs/205/
> I came to the conclusion (using minkus) that the compilation works
> with -O0 optimisation but not with -O1 optimisation, for some strange
> reason that we couldn't fathom.  (I controlled the optimisation by
> modifying the Makefile CFLAGS setting after running configure.)
> 
> I don't know how to construct a minimal case or how to further
> investigate this beyond what I have already described in that bug
> report, unfortunately.  It pretty much builds fine on all of the other
> architectures; at least none of them exhibit the same error.

I have tried to reproduce the issue, building asymptote without the fix
that went in upstream, and it now works fine with both g++-5 and g++-6.
Numerous fixes went in since this bug has been reported, I guess one of
them fixes the bug.

I am therefore closing the bug.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: