Update libdfp to 1.0.11

Bug #1459691 reported by bugproxy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
binutils (Ubuntu)
Invalid
Undecided
Unassigned
libdfp (Ubuntu)
Fix Released
Undecided
Matthias Klose

Bug Description

libdfp has received many bug fixes and new features since version 1.0.9, which is being distributed by Canonical.

libdfp 1.0.11 will be announced soon and will include important bugfixes for POWER8.

A list of differences is available at: https://github.com/libdfp/libdfp/compare/libdfp-1_0_9-branch...master

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-125558 severity-high targetmilestone-inin1510
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1459691/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → libdfp (Ubuntu)
Steve Langasek (vorlon)
Changed in libdfp (Ubuntu):
assignee: nobody → Matthias Klose (doko)
Revision history for this message
Matthias Klose (doko) wrote :

1.0.11 is not yet released

Changed in libdfp (Ubuntu):
status: New → Incomplete
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-07-13 18:23 EDT-------
Libdfp 1.0.11 is now available: https://github.com/libdfp/libdfp/releases/tag/1.0.11

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-07-22 19:37 EDT-------
This package needs to be in Debian archive in order for Canonical to include in 15.10. What is the status of that?

Revision history for this message
Matthias Klose (doko) wrote :

It doesn't matter if the package is in Debian or not.

However it fails to build. See
https://launchpad.net/ubuntu/+source/libdfp/1.0.11-0ubuntu1/+build/7715135

it successfully builds on 15.04.

gcc -DSHARED -O2 -fpic -g -mcpu=power7 -c ../sysdeps/powerpc/dfpu/isfinited32.c -D__STDC_DEC_FP__=200704L -D__STDC_WANT_DEC_FP__=1 -DOPTION_EGLIBC_LOCALE_CODE=1 -std=gnu99 -D_ISOC99_SOURCE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -Wno-long-long -include ../include/libdfp-symbols.h -include ./config.h -I../include -I../dfp -I../dfp/decimal -I../libdecnumber/dpd -I../libdecnumber -I../sysdeps/powerpc/powerpc64/power7/fpu -I../sysdeps/powerpc/powerpc64/power6/fpu -I../sysdeps/powerpc/powerpc64/power7 -I../sysdeps/powerpc/powerpc64/power6 -I../sysdeps/powerpc/powerpc64 -I../sysdeps/powerpc/dfpu -I../sysdeps/powerpc/fpu/bits -I../sysdeps/powerpc/fpu -I../sysdeps/powerpc -I../sysdeps/dpd -I../sysdeps/generic -I../decNumberMath/ -I../ieee754/ -I../base-math/ -I.. -I. -o isfinited32.o
/tmp/ccrz4Nct.s: Assembler messages:
/tmp/ccrz4Nct.s:78: Error: ignoring invalid mfcr mask
Makefile:223: recipe for target 'isfinited32.o' failed
make[1]: *** [isfinited32.o] Error 1
make[1]: Leaving directory '/home/doko/tmp/libdfp-1.0.11/build'
debian/rules:30: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2

Revision history for this message
Matthias Klose (doko) wrote :

this looks like a binutils regression on the 2.25 branch

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-07-23 20:49 EDT-------
(In reply to comment #11)
> this looks like a binutils regression on the 2.25 branch

Binutils started to detect a bad usage of mfcr.
So, this is a bug in libdfp. I'm already working on it.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-07-23 21:38 EDT-------
(In reply to comment #12)
> (In reply to comment #11)
> > this looks like a binutils regression on the 2.25 branch
>
> Binutils started to detect a bad usage of mfcr.
> So, this is a bug in libdfp. I'm already working on it.

The bug has been fixed as commit ID aa494e5b:
https://github.com/libdfp/libdfp/commit/aa494e5b73c289d7b08ecfc5195abde2f2da8fa7

doko, is this enough for you to update libdfp?

Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 1459691] Comment bridged from LTC Bugzilla

On 07/23/2015 11:41 PM, bugproxy wrote:
> The bug has been fixed as commit ID aa494e5b:
> https://github.com/libdfp/libdfp/commit/aa494e5b73c289d7b08ecfc5195abde2f2da8fa7
>
> is this enough for you to update libdfp?

I'll look at it tomorrow. Is there any way to get the diff/commit without
checking out the repository?

Matthias Klose (doko)
Changed in binutils (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libdfp - 1.0.11-0ubuntu2

---------------
libdfp (1.0.11-0ubuntu2) wily; urgency=medium

  * Fix the usage of mfcr extended mnemonic. LP: #1459691.

 -- Matthias Klose <email address hidden> Fri, 24 Jul 2015 15:37:38 +0200

Changed in libdfp (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-08-27 13:24 EDT-------
Closed at IBM side.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.