This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug time/19738] __tzfile_default 32-bit time_t overflow


https://sourceware.org/bugzilla/show_bug.cgi?id=19738

--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Paul Eggert from comment #5)
> Created attachment 9074 [details]
> more-efficient patch that uses hardware overflow flag
> 
> Attached is what I hope is a better patch, as it causes GCC to use the
> overflow flag supported by the hardware, when it is doing the integer
> overflow checking. Most of this patch is a file intprops.h that is taken
> directly from Gnulib.

If I understand correctly; this bug only triggers with custom rules that use
posixrules? How common do we think this is?

The age of the code in question means that this bug potentially exists in all
glibc's released sincd 1995 so per [1] that would be glibc 2.0 and up?

Does this bug trigger with existing posixrules or only new posixrules files
created by some recent tzdta update?

I'm trying guage the impact of this bug on the distributions.

[1] https://sourceware.org/glibc/wiki/Glibc%20Timeline

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]