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

Bug#556790: marked as done (gcc-4.3: unrecognizable insn on alpha)

Your message dated Sun, 30 May 2010 23:36:02 +0200
with message-id <[🔎] 4C02DA42.3040501@debian.org>
and subject line Re: Bug#556790: gcc-4.3: unrecognizable insn on alpha
has caused the Debian Bug report #556790,
regarding gcc-4.3: unrecognizable insn on alpha
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.)


-- 
556790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556790
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcc-4.3
Version: 4.3.4-5

Hi,

I recently started seeing several cases of gcc giving an error
message like this:
packet-l2tp.c:1680: error: unrecognizable insn:
(insn 419 86 84 9 packet-l2tp.c:1585 (set (reg:DI 200)
        (ne:SI (reg:DI 76 [ prephitmp.1208 ])
            (const_int 0 [0x0]))) -1 (nil))
packet-l2tp.c:1680: internal compiler error: in extract_insn, at recog.c:2001

The current package failing with such error are:
- wireshark
- gtk2-engines-qtcurve
- mpich2
- libssh2
- gargoyle-free

I'm not sure how old this issue is.  As far as I can see I first
saw this issue with 4.3.4-5 and 4.3.4-6 still has it.  I can
find logs of those package with 4.3.4-1 that were succesful.


Kurt

--- End Message ---
--- Begin Message --- 
Version: 4.3.5-1

On 12.12.2009 14:43, Kurt Roeckx wrote:

On Sat, Dec 12, 2009 at 12:30:57PM +0100, Kurt Roeckx wrote:

On Sat, Dec 12, 2009 at 02:33:28PM +1300, Michael Cree wrote:

What is the timeframe for getting the Alpha buildds updated to a
fixed version of gcc?


We've switched to 4.4 as default gcc a few days ago, and
the buildds are also running it already.

I've given back the packages that were known to fail, they should
get build again soon.


They were all succesful, except for wireshark which seems to
be a known issue with the package and not alpha specific.

So it's my understanding that PR8603 got applied to the>4.3.4,
4.4.2 and the 4.5 branches which "caused" PR42113 and that that
one is now fixed in the current 4.4.2 and 4.5 versions, but tht
4.3.4-6 still has this issue.
fixed upstream on the 4.3 branch as well. this should be fixed at least in 4.3.5-1 (and 4.4).

--- End Message ---
Reply to: