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

Bug#518927: marked as done (Please update dtoa.c in all packages that use it)

Your message dated Thu, 23 Jul 2020 12:11:39 +0200
with message-id <20200723101139.47ofjgktkrvbkdvq@percival.namespace.at>
and subject line Re: Please update dtoa.c in all packages that use it
has caused the Debian Bug report #518927,
regarding Please update dtoa.c in all packages that use it
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.)


-- 
518927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518927
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: general
Severity: normal

Hi,

many source packages contain the "dtoa.c" file that bears the following
copyright notice:

 * The author of this software is David M. Gay.
 *
 * Copyright (c) 1991, 2000, 2001 by Lucent Technologies.

All these packages will be miscompiled by gcc-4.4, because dtoa.c
violates strict aliasing rules. See more details at
http://patrakov.blogspot.com/2009/03/dont-use-old-dtoac.html

Please do a whole-archive search for source files (you'll mostly find
copies of dtoa.c, gdtoa.c and various internal headers) that contain the
string "#define word1(x) ((U*)&x)->L[0]", and clone this bug
accordingly.

System information: irrelevant.

Diego Elio Pettenò: you received this mail because I want you to do the
same thing for Gentoo.

-- 
Alexander E. Patrakov

--- End Message ---
--- Begin Message --- 
It would appear that after 11 years, this is either done, or there
are now individual bug reports, or it doesn't actually matter in practice.

As such, I'm thinking it is safe to close this bug now.

Thanks though!

Chris

--- End Message ---
Reply to: