aboutsummaryrefslogtreecommitdiff
path: root/libiberty/regex.c
diff options
context:
space:
mode:
authorKevin Buettner <kevinb@redhat.com>2020-07-30 20:09:05 -0700
committerKevin Buettner <kevinb@redhat.com>2020-07-31 09:33:32 -0700
commit9ef1ec5dca12fce2d9e9d3711c8a4091611c804d (patch)
treed1be5fb97d35d35ab74fe1eef34c4e3cdda35785 /libiberty/regex.c
parente6a6c7676a7df49cfbbffda26eadd2032dbc2bbe (diff)
downloadgdb-9ef1ec5dca12fce2d9e9d3711c8a4091611c804d.zip
gdb-9ef1ec5dca12fce2d9e9d3711c8a4091611c804d.tar.gz
gdb-9ef1ec5dca12fce2d9e9d3711c8a4091611c804d.tar.bz2
Fix gdb.base/corefile2.exp test case for ppc64le
It turns out that the recently added gdb.base/corefile2.exp test won't run on ppc64le linux. The test case fails the internal checks which ensure that a mmap'd region can be placed within the statically allocated regions buf_rw[] and buf_ro[]. ppc64le linux apparently has 64k pages, which is much larger than the 24k regions originally allocated for buf_rw[] and buf_ro[]. This patch increases the size of each region to 256 KiB. Tested on either rawhide or Fedora 32 for these architectures: x86_64, x86_64/-m32, ppc64le, aarch64, and s390x. gdb/testsuite/ChangeLog: * gdb.base/coremaker2.c (buf_rw): Increase size to 256 KiB. (C5_24k): Delete. (C5_8k, C5_64k, C5_256k): New macros. (buf_ro): Allocate 256 KiB of initialized data.
Diffstat (limited to 'libiberty/regex.c')
0 files changed, 0 insertions, 0 deletions