diff options
| author | Luis Machado <luis.machado@arm.com> | 2022-07-26 00:17:38 +0100 |
|---|---|---|
| committer | Arsen Arsenović <arsen@gcc.gnu.org> | 2023-08-07 22:59:38 +0200 |
| commit | a49d42e8dfe2a8ac320782c5dd2751ea3f43db68 (patch) | |
| tree | cb1ccc240a837b190cf4731db9e38d15b4107146 /libcpp | |
| parent | 24552056fd5fc677c0d032f54a5cad1c4303d312 (diff) | |
| download | gcc-a49d42e8dfe2a8ac320782c5dd2751ea3f43db68.zip gcc-a49d42e8dfe2a8ac320782c5dd2751ea3f43db68.tar.gz gcc-a49d42e8dfe2a8ac320782c5dd2751ea3f43db68.tar.bz2 | |
Disable year 2038 support on 32-bit hosts by default
With a recent import of gnulib, code has been pulled that tests and enables
64-bit time_t by default on 32-bit hosts that support it.
Although gdb can use the gnulib support, bfd doesn't use gnulib and currently
doesn't do these checks.
As a consequence, if we have a 32-bit host that supports 64-bit time_t, we'll
have a mismatch between gdb's notion of time_t and bfd's notion of time_t.
This will lead to mismatches in the struct stat size, leading to memory
corruption and crashes.
This patch disables the year 2038 check for now, which makes things work
reliably again.
I'd consider this a temporary fix until we have proper bfd checks for the year
2038, if it makes sense. 64-bit hosts seems to be more common these days, so
I'm not sure how important it is to have this support enabled and how soon
we want to enable it.
Thoughts?
ChangeLog:
* configure.ac: Disable year2038 by default on 32-bit hosts.
* configure: Regenerate.
Diffstat (limited to 'libcpp')
0 files changed, 0 insertions, 0 deletions