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

Bug#760113: marked as done (gcc-4.9: [sh4] Invalid operands for opcode div0s)

Your message dated Wed, 08 Oct 2014 09:00:45 +0200
with message-id <5434E11D.3000507@debian.org>
and subject line Re: Bug#760113: gcc-4.9: [sh4] Invalid operands for opcode div0s
has caused the Debian Bug report #760113,
regarding gcc-4.9: [sh4] Invalid operands for opcode div0s
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.)


-- 
760113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760113
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcc-4.9
Version: 4.9.1-11
Severity: normal
Tags: upstream

Hello!

gcc-4.9 currently creates invalid assembly code on sh4 due to a
regression. This mainly affects postgresql-9.4 which fails to build
from source due to this bug [1].

Upstream has already acknowledged the bug and proposed a patch to fix
the problem, see [2]. Just filing it here to be able to track the problem
better.

Cheers,
Adrian

> [1] http://buildd.debian-ports.org/status/fetch.php?pkg=postgresql-9.4&arch=sh4&ver=9.4~beta2-1&stamp=1409261773
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62312

--- End Message ---
--- Begin Message --- 
Version: 4.9.1-16

Am 31.08.2014 um 23:44 schrieb John Paul Adrian Glaubitz:
> Package: gcc-4.9
> Version: 4.9.1-11
> Severity: normal
> Tags: upstream
> 
> Hello!
> 
> gcc-4.9 currently creates invalid assembly code on sh4 due to a
> regression. This mainly affects postgresql-9.4 which fails to build
> from source due to this bug [1].
> 
> Upstream has already acknowledged the bug and proposed a patch to fix
> the problem, see [2]. Just filing it here to be able to track the problem
> better.

fixed upstream

--- End Message ---
Reply to: